[
https://issues.apache.org/jira/browse/SPARK-8377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710855#comment-14710855
]
Santiago M. Mola commented on SPARK-8377:
-----------------------------------------
Right. However, there is no distinction between an identifier that was quoted
by the user and one that was not. So the user intent is lost. If we see "a", we
don't know if the user wanted strictly "a" or case insensitive "a". So if we
have a column "a" and a column "A", which one should we match?
> Identifiers caseness information should be available at any time
> ----------------------------------------------------------------
>
> Key: SPARK-8377
> URL: https://issues.apache.org/jira/browse/SPARK-8377
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Reporter: Santiago M. Mola
>
> Currently, we have the option of having a case sensitive catalog or not. A
> case insensitive catalog just lowercases all identifiers. However, when
> pushing down to a data source, we lose the information about if an identifier
> should be case insensitive or strictly lowercase.
> Ideally, we would be able to distinguish a case insensitive identifier from a
> case sensitive one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
