-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
make page filter public #6523
make page filter public #6523
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a fine change in my mind -- @jiacai2050 can you comment about why you would like to have this API public ? I didn't see any rationale or a linked ticket?
Also if you want to use this API long term I suggest we implement an end to end test (maybe in datafusion/core/tests/parquet somewhere) for it so that it isn't broken accidentally in some future refactor
@alamb Thanks, I'm still testing this changeset in CeresDB, I will add more context once I'm done.
Agreed! |
This PR still says "WIP" in the title so I am not sure if you think it is ready to merge @jiacai2050 -- or if you plan to work on an end to end test before doing so? |
I believe if you merge up to latest main branch the clippy failure has been resolved. |
It appears that |
THanks @jiacai2050 |
* make page_filter public * make parquet public * fix CI
Which issue does this PR close?
Closes #.
Rationale for this change
We at CeresDB are using a customized parquet reader based on parquet-rs for some historical reason, in order to reuse those page prune functions from datafusion, those interface should be public.
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?