-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Namespace names with dot(.) not supported by JDBC catalog when listing namespaces #11990
Comments
@mingnuj can you please share which issue you ran into? Any stack traces and error messages will help |
Thank you for your response. I'm sorry for not clarifying where the issue occurs. The problem arises when retrieving the namespace. When I connect to the database and use the Is there any way to resolve this issue? |
I checked and it turns out that this isn't an issue with the REST catalog but rather with the JDBC catalog itself. The problematic piece of code is here:
This can be reproduced by updating
and running /cc @jbonofre |
Query engine
REST API (JAVA)
Question
I am using the Iceberg REST API(tabulario/iceberg-rest) with PostgreSQL JDBC as the backend catalog. However, I have encountered an issue where namespace names containing
.
are not supported.I have verified that namespaces with
.
are correctly stored and retrieved in the PostgreSQL database. From my observation, the REST API seems to interpret.
in namespace names as levels by default.I could not find any mention in the specification that namespace names with
.
are disallowed. Moreover, when using double quotes ("
) in the database, it is possible to use.
in namespace names. I think it would be better to allow this in the REST API as well.PostgreSQL Configuration:
REST API Configuration:
Created
[email protected]
namespace andtest
table in that.Namespace Display in PostgreSQL:
Could you confirm whether this is the intended behavior or a bug? If possible, I would like to request support for namespace names containing
.
.The text was updated successfully, but these errors were encountered: