-
Notifications
You must be signed in to change notification settings - Fork 299
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
[Bug report] Catalog backend name handle the renaming of catalog #4718
Comments
@FANNG1 Could you take a look? |
thanks for reporting, I'll take it |
@diqiu50 @jerqi @jerryshao WDYT? |
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 |
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? |
Maybe used for test? I'm not sure
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 |
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
The text was updated successfully, but these errors were encountered: