[
https://issues.apache.org/jira/browse/FLINK-12624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-12624:
-----------------------------------
Labels: auto-deprioritized-major pull-request-available stale-minor (was:
auto-deprioritized-major pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Make Flink case-insensitive to meta object names
> ------------------------------------------------
>
> Key: FLINK-12624
> URL: https://issues.apache.org/jira/browse/FLINK-12624
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Reporter: Bowen Li
> Priority: Minor
> Labels: auto-deprioritized-major, pull-request-available,
> stale-minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> currently Flink is case-sensitive to meta object names. For example, for
> table names, "t1" and "T1" are two distinct tables in Flink.
> There are two main reasons to make Flink case-insensitive to such names.
> 1) To make it more user-friendly for SQL users. Most popular databases
> nowadays are case insensitive to meta object names, to tolerate user typos in
> SQL commands and reduce usage friction
> 2) We chose Hive metastore as the main persistent catalog, and Hive metastore
> is case insensitive.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
