[ 
https://issues.apache.org/jira/browse/TAJO-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733680#comment-14733680
 ] 

Hudson commented on TAJO-1820:
------------------------------

SUCCESS: Integrated in Tajo-master-build #840 (See 
[https://builds.apache.org/job/Tajo-master-build/840/])
TAJO-1820: Fix wrong case sensitivity rules of non-reserved keywords. (hyunsik: 
rev c0e193d71ba3bf478d352b0a341d12ac6c8ac1d2)
* CHANGES
* 
tajo-core-tests/src/test/resources/results/TestSQLAnalyzer/case_sensitivity1.result
* 
tajo-core-tests/src/test/resources/queries/TestSQLAnalyzer/case_sensitivity1.sql
* tajo-core/src/main/java/org/apache/tajo/parser/sql/SQLAnalyzer.java


> Fix wrong case sensitivity rules of non-reserved keywords
> ---------------------------------------------------------
>
>                 Key: TAJO-1820
>                 URL: https://issues.apache.org/jira/browse/TAJO-1820
>             Project: Tajo
>          Issue Type: Bug
>          Components: Planner/Optimizer, SQL Parser
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.11.0
>
>
> For example, in the following DDL statements, {{default}} database name is 
> recognized as {{DEFAULT}} instead of {{default}}.
> {code}
> CREATE TABLE DEFAULT.TABLE1 (xxx INT, ...
> {code}
> The main reason is {{default}} is non-reserved keywords. So, it is not passed 
> through the same case sensitive handling code. So, we should fix it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to