Samrat002 commented on PR #206:
URL:
https://github.com/apache/flink-connector-aws/pull/206#issuecomment-2886038191
> Hey Samrat. How could we encapsulate this specific issues? From user
perspective we are already limiting them creating tables and databases with
uppercase. In regards of the schema, we encapsulate storing the actual original
columnNames in column parameters in Glue, so even though user sees their schema
in glue with lower case (default for glue). we actually leverage the original
column name.
Thanks for the detailed response.
Can you help me understand the technical complexity to support
CaseSensitivity from GlueCatalog?
This is a deviation.
I believe understanding how other connectors or catalogs handle mismatches,
there can be a couple of ways to handle it
1. Surfacing the mismatch to the end user with constraints
2. Handling it in FlinkCatalog to provide consistent behaviour.
We can start a thread in the community to discuss this approach.
I am fine with either of the approaches as long as the community agrees on
it.
--
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
