gaborkaszab commented on PR #16069: URL: https://github.com/apache/iceberg/pull/16069#issuecomment-4296572270
Hi @lunar-shadow , thanks for the PR! I'm trying to think it through how this would work with catalog server implementations that preserve the case of the names. E.g. these might cause some headaches: 1) If we have a table with a mixed case name in the catalog (e.g. MyTable) then we won't be able to query it after turning this feature on 2) There could be other engines writing tables into the catalog that don't use this feature. As a result there is no guarantee that whatever tables are created by those other engines are accessible with the one with the future turned on. 2) There could be different tables in the catalog with names where only the case is different. E.g. `mytable`, `MYTABLE`, `MyTable` etc. If the user queries for `MyTable` and has this feature on as `lower_case` then the user might get a different table than expected. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
