Skip to content

update v1 endpoints to use carrara #37

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

Open
wants to merge 16 commits into
base: master
Choose a base branch
from
Open

Conversation

st4tdb
Copy link
Collaborator

@st4tdb st4tdb commented May 8, 2025

This PR updates the client to use the carrara endpoints for v1 only at the moment. The build.gradle has been changed to use the SNAPSHOT channel for pre-releases until carrara is out

@st4tdb st4tdb force-pushed the st4tdb/update_endpoints branch from 82031b8 to ce75b6f Compare May 8, 2025 19:31
@st4tdb st4tdb force-pushed the st4tdb/update_endpoints branch from ce75b6f to a8f1f04 Compare May 8, 2025 19:35
@st4tdb st4tdb changed the title St4tdb/update endpoints update v1 endpoints to use carrara May 8, 2025
@st4tdb st4tdb marked this pull request as ready for review May 8, 2025 20:56
@st4tdb st4tdb requested review from Shelnutt2 and ihnorton May 8, 2025 20:56
@ihnorton ihnorton requested a review from ryan-williams May 9, 2025 01:41
Copy link
Member

@ryan-williams ryan-williams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple questions… I'm also unclear which of these diffs are due to:

  • Changed openapi-generator version
  • Bumped core version (2.2.19 to 2.17.51)
  • Other changes introduced manually

I'm new to this repo, so any context you can provide for understanding the "big picture" would be appreciated, ty!

src/test/java/io/tiledb/cloud/rest_api/model/UDFTypeTest.java
src/test/java/io/tiledb/cloud/rest_api/model/UserTest.java
src/test/java/io/tiledb/cloud/rest_api/model/WriterTest.java
src/main/java/org/openapitools/client/ApiCallback.java
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these "renames" intentional?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@@ -1 +1 @@
7.7.0
6.0.1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be good to use the same version, to rule out spurious diffs introduced by a changed version.

Looks like 7.12.0 is latest, atm, but I'd suggest changing the version as a separate PR

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. I think it is better if we use the latest version in a separate PR

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about just using the same version that was previously used? (7.7.0)

Just trying to rule out introducing spurious changes from going backwards on the version here.

@st4tdb
Copy link
Collaborator Author

st4tdb commented May 12, 2025

Many changes are just dates or doc changes. Everything is auto generated. We have decided that when this gets merged to main it will act as the dev branch for the new server. We will then need to add tests etc. It is in a very preliminary form now, and will be mainly used for the udfs

@st4tdb st4tdb requested a review from ryan-williams May 12, 2025 21:02
@st4tdb
Copy link
Collaborator Author

st4tdb commented May 12, 2025

The stable and current version has been branched here. https://github.com/TileDB-Inc/TileDB-Cloud-Java/tree/release-0.5.0

Copy link
Member

@ryan-williams ryan-williams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry if I've missed it: are the command(s) you used for this documented somewhere?

I skimmed the changes and they seem reasonable, but I'm missing some context about how the changes were generated.

@@ -1 +1 @@
7.7.0
6.0.1
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about just using the same version that was previously used? (7.7.0)

Just trying to rule out introducing spurious changes from going backwards on the version here.

@ryan-williams ryan-williams force-pushed the st4tdb/update_endpoints branch from 8f9dcf8 to 45e0da0 Compare May 16, 2025 02:11
Update local copy of spec from [`TileDB-Server//openapi/v1to3/src/openapi-v1.yaml`](https://github.com/TileDB-Inc/TileDB-Server/blob/main/openapi/v1to3/src/openapi-v1.yaml):
```bash
gh api \
  -H "Accept: application/vnd.github.raw" \
   /repos/TileDB-Inc/TileDB-Server/contents/openapi/v1to3/src/openapi-v1.yaml \
> openapi-v1.yaml
```
@ryan-williams
Copy link
Member

@st4tdb my only remaining concern here is with 1f076eb (rm TileDB{SQL,UDF}.java, update Examples.java).

Some of the existing examples were broken, seemingly to do with new "workspace" prefix in tiledb:// URIs, and I saw you had just deleted those examples, so I did the same.

  • Should those examples be salvaged in some way? Or any TODOs I should add?
  • Were TileDB{SQL,UDF}.java unnecessary?

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

Successfully merging this pull request may close these issues.

3 participants