You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2021/12/07 19:17:34 UTC

[GitHub] [iceberg] yyanyy commented on pull request #3668: AWS: Remove namespace validation from GlueCatalog's isValidIdentifier

yyanyy commented on pull request #3668:
URL: https://github.com/apache/iceberg/pull/3668#issuecomment-988200101


   Do we know which engine would encounter issue with a more relaxing database name? I think the point "since at that time the database likely already existed (if not created using Iceberg library)" mentioned in the PR description is the main reason, as otherwise it could be a confusing experience if the user wants to create a table with a preexisting database and we fail validation because of the database name. At least it would be good if we print out exactly which part of the table identifier was violating the rule. 
   
   It definitely would be the best if we can get an answer from Glue team on why we have such inconsistency and the path forward. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org