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

Reimplement parquet I/O according to HATS plans #163

Open
1 of 3 tasks
hombit opened this issue Oct 30, 2024 · 0 comments
Open
1 of 3 tasks

Reimplement parquet I/O according to HATS plans #163

hombit opened this issue Oct 30, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@hombit
Copy link
Collaborator

hombit commented Oct 30, 2024

Feature request

With HATS, we plan to serialize nested columns as a set of list-columns and include metadata for reconstruction: astronomy-commons/lsdb#466

To support this, we could modify our custom to/read_parquet implementations accordingly. It is not yet clear where HATS will store metadata that maps list-columns back to their respective nested columns. Here, we can explore the possibility of storing this information within the parquet metadata.

Before submitting
Please check the following:

  • I have described the purpose of the suggested change, specifying what I need the enhancement to accomplish, i.e. what problem it solves.
  • I have included any relevant links, screenshots, environment information, and data relevant to implementing the requested feature, as well as pseudocode for how I want to access the new functionality.
  • If I have ideas for how the new feature could be implemented, I have provided explanations and/or pseudocode and/or task lists for the steps.
@hombit hombit added the enhancement New feature or request label Oct 30, 2024
@hombit hombit changed the title Reimplement parquet I/O Reimplement parquet I/O according to HATS plans Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant