[
https://issues.apache.org/jira/browse/SPARK-16049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15339905#comment-15339905
]
Yin Huai commented on SPARK-16049:
----------------------------------
Actually, the parser already turns those partition keys to their lowercase
forms
(https://github.com/apache/spark/blob/branch-2.0/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/plans/logical/basicLogicalOperators.scala#L372).
So nothing is actually broken when case-insensitive resolution is used. Let me
close this jira. We can revisit this issue when we work on the case-sensitivity
story.
> Make InsertIntoTable's expectedColumns support case-insensitive resolution
> properly
> -----------------------------------------------------------------------------------
>
> Key: SPARK-16049
> URL: https://issues.apache.org/jira/browse/SPARK-16049
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Reporter: Yin Huai
>
> Right now, InsertIntoTable's expectedColumns uses the method of {{contains}}
> to find static partitioning columns. When analyzer is case-insensitive, the
> initialization of this lazy val will not work as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
