Open jerqi opened 2 weeks ago
@FANNG1 Could you take a look?
thanks for reporting, I'll take it
jdbc
as the default catalog name, as Iceberg REST server doesn't have something like catalog id.@diqiu50 @jerqi @jerryshao WDYT?
What are the problems with using jdbc as the default catalog name?
What are the problems with using jdbc as the default catalog name?
The two catalogs with the same JDBC URI will share the same table.
It feels like this is not a reasonable usage.
If the user wants to use one MySQL, at least the database name for Iceberg catalogs should not be the same
database is included in the uri
for JDBC backend.
Why do two Iceberg catalogs need to use the same database? Do users expect these two catalogs to be able to see each other's tables?
Why do two Iceberg catalogs need to use the same database?
Maybe used for test? I'm not sure
Do users expect these two catalogs to be able to see each other's tables?
I'm not sure, What do you think?
I think it maybe used for test.
@diqiu50 , could you summarize your point about the proposed changes?
I think that if the user sets the catalog.backend.name
, it should use the user's setting; otherwise, it should use the default
Version
main branch
Describe what's wrong
Currenlty, Iceberg jdbc backend will use catalog name as default backend name. In my understanding, it will trigger the bug if I rename the catalog.
Error message and/or stacktrace
From the code.
How to reproduce
I have questions when I read the code
Additional context
No response