-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Nested namespace support is broken in 1.7.0 #11539
Comments
@mayankvadariya can you provide additional details against which REST server this is running? Are there any reproducible tests in Trino itself to easily run & reproduce this? |
Currently I cannot reproduce this issue with the below Trino test:
|
I can reproduce this if I use Trino w/ Iceberg 1.7(commit |
Polaris hits the same issue. The potential fix seems a good candidate for 1.7.1. |
@nastra Please place and run below test in TestIcebergPolarisCatalogConnectorSmokeTest. Include @Test
void testNestedNamespace()
{
assertUpdate("CREATE SCHEMA level1");
assertUpdate("CREATE SCHEMA \"level1.level2\"");
assertThat(computeActual("SHOW SCHEMAS").getOnlyColumnAsSet())
.containsExactlyInAnyOrder(
"information_schema",
"tpch",
"level1",
"level1.level2");
} |
The namespace encoding change was reverted with #11574. |
@mayankvadariya I'm going to close this, the change will be 1.7.1 in case you have a chance to test. |
Apache Iceberg version
1.7.0 (latest release)
Query engine
Trino
Please describe the bug 🐞
Nested namespace request to Iceberg catalog server is sent incorrectly after upgrading Iceberg library from 1.6.1 to 1.7.0 in Trino. I've provided further analysis in #10858 (comment)
After trinodb/trino@ead6d9f commit(which bumps Iceberg from 1.61. to 1.7.0),
show schemas
fails in Iceberg connector with below error.Willingness to contribute
The text was updated successfully, but these errors were encountered: