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

ContentKey based filter in the Nessie Diff API #3957

Closed
harshm-dev opened this issue Apr 14, 2022 · 1 comment · Fixed by #6743
Closed

ContentKey based filter in the Nessie Diff API #3957

harshm-dev opened this issue Apr 14, 2022 · 1 comment · Fixed by #6743
Labels

Comments

@harshm-dev
Copy link
Contributor

Description: The current diff API brings the differences in all content keys between the two perimeters. The request is to allows a filter that restricts the search operation for a specific ContentKey.
The DBAdapter implementation is already equipped to take KeyFilterPredicate parameter. So, the ask to expose the same at upper layers (version store / APIs etc).

Requested Changes in public API: Extend diff API to support filter options on the content key

  • Changes in REST API
  • Changes in Java Client API
  • Changes in Python Client API
  • Changes in SQL extentions

Expected Use Cases: Skip compaction on unchanged tables

@snazy snazy added the REST api label Sep 6, 2022
@snazy snazy mentioned this issue Sep 6, 2022
21 tasks
@dimas-b
Copy link
Member

dimas-b commented Dec 8, 2022

This is a general enhancement (applies to API v1 as well as to v2), so I'm moving it out of the scope of #5112, which contains only the tasks required to achieve a releasable API v2 covering existing v1 functionality (where possible).

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 a pull request may close this issue.

3 participants