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 start/end key parameters to v2 API methods #5591

Closed
dimas-b opened this issue Dec 1, 2022 · 0 comments · Fixed by #6743
Closed

Add start/end key parameters to v2 API methods #5591

dimas-b opened this issue Dec 1, 2022 · 0 comments · Fixed by #6743
Assignees
Labels

Comments

@dimas-b
Copy link
Member

dimas-b commented Dec 1, 2022

With some incoming storage model improvements, Nessie can return results not only for a collection of fixed keys but also for key ranges.

Start/end key boundaries are meaningful in these TreeApi v2 methods:

  • getEntries
  • getDiff

Potentially later:

  • getReferences (?)

Likely not happening soon:

  • getSeveralContents
  • getMultipleContents
This was referenced Dec 1, 2022
@snazy snazy added the REST api label Dec 1, 2022
@dimas-b dimas-b self-assigned this Dec 6, 2022
dimas-b added a commit to dimas-b/nessie that referenced this issue Dec 8, 2022
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
dimas-b added a commit to dimas-b/nessie that referenced this issue Dec 8, 2022
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
dimas-b added a commit to dimas-b/nessie that referenced this issue Dec 8, 2022
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
@dimas-b dimas-b mentioned this issue Dec 20, 2022
15 tasks
snazy pushed a commit to snazy/nessie that referenced this issue May 4, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 4, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 5, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 6, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 9, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 10, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 10, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 10, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 11, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 13, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 13, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 17, 2023
* In "diff" API

* In "get entries"

* New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy pushed a commit to snazy/nessie that referenced this issue May 17, 2023
* In "diff" API

* In "get entries"

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes projectnessie#5591
snazy added a commit that referenced this issue May 17, 2023
* Add key range parameters to REST API v2

* In "diff" API

* In "get entries"

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes #5591

Co-authored-by: Dmitri Bourlatchkov <dmitri.bourlatchkov@dremio.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants