[ 
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 auto-deprioritized-minor 
pull-request-available  (was: auto-deprioritized-major pull-request-available 
stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any 
updates so it is being deprioritized. If this ticket is actually Minor, please 
raise the priority and ask a committer to assign you the issue or revive the 
public discussion.


> 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: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor, 
> pull-request-available
>          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)

Reply via email to