-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
Cache Parquet metadata in pg_analytics
#57
Comments
interesting. I would like to work on this issue. Before that let me take a look at the codebase. |
It’s yours! |
Hey @philippemnoel I am finding it hard to allocate time for this issue. Since this is marked as high priority. Please feel free to re-assign this issues to someone else |
Sounds good! |
Hi @philippemnoel, I am interested to work on this. Could you please assign it to me. |
Yes |
Done! Excited to see :) |
Hi @philippemnoel, Could you please reassign the issue to me?
Thank you! |
Done! Really exciting stuff, I had removed you since you were still working on the partition PR. Excited to see it! |
What feature are you requesting?
DuckDB has a feature,
enable_object_cache
, which can cache Parquet metadata in-memory. This is known to improve query performance. We would like to cache this on-disk, so that it can persist across queries.Why are you requesting this feature?
See above ^
What is your proposed implementation for this feature?
I'm not sure, see #30 for reference
Full Name:
Philippe Noël
Affiliation:
ParadeDB
The text was updated successfully, but these errors were encountered: