-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Bump Iceberg and Nessie versions #21034
Conversation
@@ -126,7 +128,11 @@ protected void commitToExistingTable(TableMetadata base, TableMetadata metadata) | |||
{ | |||
verify(version.orElseThrow() >= 0, "commitToExistingTable called on a new table"); | |||
try { | |||
nessieClient.commitTable(base, metadata, writeNewMetadata(metadata, version.getAsInt() + 1), table, toKey(new SchemaTableName(database, this.tableName))); | |||
if (table == null) { | |||
table = nessieClient.table(toIdentifier(new SchemaTableName(database, tableName))); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's not clear to me why these changes are necessary
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nessieClient.commitTable
signature has changed. It just needs contentID instead of expected content.
ExpectedContent
(aka table) was null before this PR also for commitToExistingTable
. I have debug the original integration to understand it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM but it's not clear why the changes in IcebergNessieTableOperations
are necessary
Pls provide relevant code link in the 1.5.0 tag of the Iceberg code. The I'm not sure though that apache/iceberg#9592 is the cause for the extra |
@wendigo could you please run the PR with secrets to see the output of the cloud tests as well? |
/test-with-secrets sha=054aecc7acca690b80e048a7647c26924bb42fb8 |
The CI workflow run with tests that require additional secrets has been started: https://github.com/trinodb/trino/actions/runs/8256356235 |
...eberg/src/main/java/io/trino/plugin/iceberg/catalog/nessie/IcebergNessieTableOperations.java
Outdated
Show resolved
Hide resolved
...eberg/src/main/java/io/trino/plugin/iceberg/catalog/nessie/IcebergNessieTableOperations.java
Outdated
Show resolved
Hide resolved
...eberg/src/main/java/io/trino/plugin/iceberg/catalog/nessie/IcebergNessieTableOperations.java
Outdated
Show resolved
Hide resolved
...eberg/src/main/java/io/trino/plugin/iceberg/catalog/nessie/IcebergNessieTableOperations.java
Outdated
Show resolved
Hide resolved
SchemaTableName schemaTableName = new SchemaTableName(databaseName, tableName); | ||
return ContentKey.of(Namespace.parse(schemaTableName.getSchemaName()), schemaTableName.getTableName()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not pass databaseName & tableName to Namespace.parse()
directly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we miss the validation of empty schemaname and conversion of the identifiers into lower case.
I don't know the background. But I assumed it was written for that purpose. So, retained the SchemaTableName
@findinpath I can confirm that those extra |
plugin/trino-iceberg/src/test/java/io/trino/plugin/iceberg/TestIcebergFileOperations.java
Outdated
Show resolved
Hide resolved
LGTM @findepi @findinpath do you want to chime in? |
plugin/trino-iceberg/src/main/java/io/trino/plugin/iceberg/fileio/ForwardingFileIo.java
Show resolved
Hide resolved
- Bump Iceberg to 1.5.0 and Nessie to 0.77.1 - Remove deprecated usage - Fix regression when reading manifest file by overriding newInputfile and passing in the known length Co-authored-by: amogh-jahagirdar <[email protected]>
This has no user facing impact and therefore needs to release notes entry? Can you confirm @wendigo and @ajantha-bhat ? |
I don't remember mentioning Nessie version bumps in the release notes. |
@mosabua No need to mention in the release note. |
Description
Additional context and related issues
https://iceberg.apache.org/releases/#150-release
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.