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 support for row filtering #16955

Closed

Conversation

agrawalreetika
Copy link
Member

== RELEASE NOTES ==

General Changes
* Add support for row level filtering

@pettyjamesm
Copy link
Contributor

This appears to be code extracted from trinodb/trino#2891, specifically trinodb/trino@7efb49c. Please review the commit guidelines related to attribution and update the commit accordingly

@agrawalreetika agrawalreetika force-pushed the row-filtering-support branch 2 times, most recently from b697008 to 9fc48c1 Compare November 9, 2021 06:12
@stale
Copy link

stale bot commented Jun 13, 2022

This pull request has been automatically marked as stale because it has not had recent activity. If you'd still like this PR merged, please comment on the task, make sure you've addressed reviewer comments, and rebase on the latest master. Thank you for your contributions!

@stale stale bot added the stale label Jun 13, 2022
@agrawalreetika agrawalreetika force-pushed the row-filtering-support branch from 9fc48c1 to dbac1e4 Compare June 15, 2022 08:15
@agrawalreetika agrawalreetika requested a review from a team as a code owner June 15, 2022 08:15
@stale stale bot removed the stale label Jun 15, 2022
@agrawalreetika
Copy link
Member Author

@pettyjamesm Would you be able to help me review this PR?

Cherry-pick of trinodb/trino@7efb49c
Co-authored-by: Martin Traverso <[email protected]>
@prestoprobot
Copy link

@presto-oss Friendly ping. Please review this PR. Thank you!

@agrawalreetika
Copy link
Member Author

Closing in favor of #24277

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

Successfully merging this pull request may close these issues.

4 participants