[
https://issues.apache.org/jira/browse/TAJO-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14733508#comment-14733508
]
ASF GitHub Bot commented on TAJO-1820:
--------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/741
TAJO-1820: Fix wrong case sensitivity rules of non-reserved keywords.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-1820
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/741.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #741
----
commit c092bec961048a1884782772c323d8440382c8df
Author: Hyunsik Choi <[email protected]>
Date: 2015-09-07T10:16:59Z
TAJO-1820: Fix wrong case sensitivity rules of non-reserved keywords.
----
> 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)
