[
https://issues.apache.org/jira/browse/FLINK-16175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17067748#comment-17067748
]
Leonard Xu commented on FLINK-16175:
------------------------------------
Hi [~dwysakowicz]
I open a WIP PR only for column name case-sensitive, as for meta object
name(catalog/database/table), I found
org.apache.calcite.jdbc.SimpleCalciteSchema#getImplicitTable(String name,
boolean caseSensitive) can not deal the caseSensitive flag because interface
org.apache.calcite.schema.Schema only has getTable(String name) function. It's
hard to walk around this question or find a clean solution after offline
discussed with [~godfreyhe] who is an expert in this field.
I'm considering to open an issue to add `getXXX(String name, boolean
caseSensitive)` in Schema in calcite community, and then we can support
caseSensitive for meta object naturally. What do you think?
> Add config option to switch case sensitive for column names in SQL
> ------------------------------------------------------------------
>
> Key: FLINK-16175
> URL: https://issues.apache.org/jira/browse/FLINK-16175
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / API, Table SQL / Planner
> Affects Versions: 1.11.0
> Reporter: Leonard Xu
> Assignee: Leonard Xu
> Priority: Major
> Labels: pull-request-available, usability
> Fix For: 1.11.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Flink SQL is default CaseSensitive and have no option to config. This issue
> aims to support
> a configOption so that user can set CaseSensitive for their SQL.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
