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.

Sign up for GitHub

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

Jump to bottom

API v2 #5112

Closed
21 tasks done
snazy opened this issue Sep 6, 2022 · 1 comment
Closed
21 tasks done

API v2 #5112

snazy opened this issue Sep 6, 2022 · 1 comment
Assignees
@dimas-b
Labels
java Pull requests that update Java code python Pull requests that update Python code REST api ui Code changes related to UI website projectnessie.org website related

Comments

@snazy
Copy link
Member

snazy commented Sep 6, 2022 •
edited
Loading

Umbrella ticket for all API v2 tickets & PRs.

The current REST API has some shortcomings that we want to address before (or for) Nessie 1.0 GA.
@snazy snazy added python Pull requests that update Python code java Pull requests that update Java code REST api ui Code changes related to UI website projectnessie.org website related labels Sep 6, 2022
@snazy snazy mentioned this issue Sep 6, 2022
Closed
@dimas-b dimas-b mentioned this issue Oct 3, 2022
Closed
@dimas-b dimas-b mentioned this issue Oct 21, 2022
Closed
dimas-b added a commit to dimas-b/nessie that referenced this issue Oct 27, 2022
@dimas-b
Add API v2
b46b86a 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
@dimas-b dimas-b mentioned this issue Oct 27, 2022
Merged
dimas-b added a commit to dimas-b/nessie that referenced this issue Oct 27, 2022
@dimas-b
Add API v2
2d6b48e 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 2, 2022
@dimas-b
Add API v2
beeb829 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 3, 2022
@dimas-b
Add API v2
5ebf5cf 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 3, 2022
@dimas-b
Add API v2
063e84d 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 7, 2022
@dimas-b
Add API v2
1e9b844 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 7, 2022
@dimas-b
Add API v2
9e1c6e5 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 8, 2022
@dimas-b
Add API v2
2284467 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 8, 2022
@dimas-b
Add API v2
7ce30f7 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 9, 2022
@dimas-b
Add API v2
126d027 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 10, 2022
@dimas-b
Add API v2
c0330f4 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 10, 2022
@dimas-b
Add API v2
6e3a706 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 11, 2022
@dimas-b
Add API v2
e4fc40b 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
@dimas-b dimas-b mentioned this issue Nov 14, 2022
Closed
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 14, 2022
@dimas-b
Add API v2
585fb9e 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 15, 2022
@dimas-b
Add API v2
fa79aad 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 22, 2022
@dimas-b
Add API v2
6028226 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only for v2. OpenAPI for v1
should be obtained from older Nessie publications.

This is the main contribution towards projectnessie#5112
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 30, 2022
@dimas-b
Add API v2
139704f 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only boith v1 and v2 endpoints,
which changes the old relative paths for v1 to have an explicit /v1
prefix.

This is the main contribution towards projectnessie#5112

* It is not necessary to run V2 Reaseasy tests on all backends.
  In-memory tests are sufficient.
dimas-b added a commit to dimas-b/nessie that referenced this issue Nov 30, 2022
@dimas-b
Add API v2
d3d3583 
Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

OpenAPI YAML is built and published only boith v1 and v2 endpoints,
which changes the old relative paths for v1 to have an explicit /v1
prefix.

This is the main contribution towards projectnessie#5112

* It is not necessary to run V2 Reaseasy tests on all backends.
  In-memory tests are sufficient.
dimas-b added a commit that referenced this issue Dec 1, 2022
@dimas-b
Add REST API v2 (#5004)
b8f6e4d 
This is the main contribution towards #5112

* Add API v2

Add v2 REST endpoints.

Add java client implementation for v2 REST API.

Since namespaces are treated as ordinary content objects in API v2
the old java client API for dealing with namespaces is implemented
on the client side on top of v2 "get entries" and "commit" APIs.

* Run in-memory REST server tests for both v1 and v2 APIs.

REST test using persistent backend only use v2 API.

Resteasy test remain on v1 API since they construct REST requests
according to Nessie API v1 specs.

It is not necessary to run V2 Reaseasy tests on all backends.
In-memory tests are sufficient.

* OpenAPI YAML is built and published only boith v1 and v2 endpoints,
which changes the old relative paths for v1 to have an explicit /v1
prefix.
@dimas-b dimas-b mentioned this issue Dec 6, 2022
Closed
15 tasks
@dimas-b
Copy link
Member

dimas-b commented Dec 6, 2022

Moved some sub-tasks to #5645

@dimas-b dimas-b mentioned this issue Dec 8, 2022
Closed
@snazy snazy closed this as completed May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dimas-b dimas-b

Labels
java Pull requests that update Java code python Pull requests that update Python code REST api ui Code changes related to UI website projectnessie.org website related
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@snazy @dimas-b