nicusX commented on PR #206: URL: https://github.com/apache/flink-connector-aws/pull/206#issuecomment-2915317163
@Samrat002 @FranMorilloAWS about case sensitivity, these are the logical rules I suggest: 1. the actual case should preserved for **all supported objects** and used consistently in Flink interface, e.g. in`CREATE TABLE...` but also `SHOW TABLE`, `SHOW COLUMNS ...` etc. From a user's perspective, the way object names are actually stored in Glue should not be a concern. 2. The additional metadata should be stored in Glue in a consistent way for all object types. `Parameters` seems to be available for Database, Tables, and Columns in Glue. A problem arises for Functions which don't have any `Parameters` if I am not mistaken. 3. The additional metadata should not leak into Flink user interface. The "originalName" should not pop up in a `SHOW TABLES` or `SHOW COLUMNS` 4. The fact Glue UI is limited and only shows lowercase names is not a concern of this component's I would add that the way the additional metadata (the original name and any additional info required) is stored in Glue should be clearly documented, in case a user want's to build their own external interface to extract or update information in the Glue Catalog. -- 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-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
