Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add brief description of how partitioned data currently works/doesn't work #212

Open
nickreich opened this issue Nov 13, 2024 · 1 comment

Comments

@nickreich
Copy link
Contributor

Add some content in the hub structure documentation page that describes how the current data partitioning set-up does and does not work with current hubverse infrastructure. And maybe something about how this is not an active development priority for the hubverse so using this functionality is "as is". We could link to the SMH hub that has done some of this. And also mention that further hubverse development might focus on cloud-based storage without GitHub which would get around GitHub file size limits, which is one of the reasons we've considered this at all.

@matthewcornell
Copy link

matthewcornell commented Nov 13, 2024

Here's the partition documentation from hubData's connect_hub():

partitions: a named list specifying the arrow data types of any partitioning column.

Default:

partitions = list(model_id = arrow::utf8()),

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

2 participants