REST: Set fresh IDs on create-table #327
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For the other implementation we do this when writing the metadata, but for the REST catalog we just post the schema itself. The REST spec does not mention anything about setting fresh IDs, so it is best to do it ourselves.
rdblue
reviewed
Jan 30, 2024
|
|
||
| namespace_and_table = self._split_identifier_for_path(identifier) | ||
| request = CreateTableRequest( | ||
| name=namespace_and_table["table"], | ||
| location=location, | ||
| table_schema=schema, | ||
| table_schema=iceberg_schema, |
There was a problem hiding this comment.
Isn't this done on the server side?
There was a problem hiding this comment.
Yes, but some server sides still require the IDs to be unique
rdblue
approved these changes
Jan 30, 2024
|
Thanks for the prompt review @rdblue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the other implementations, we do this when writing the metadata, but for the REST catalog, we post the schema itself.
The REST spec does not mention anything about setting fresh IDs, so it is best to do it ourselves.