[
https://issues.apache.org/jira/browse/TAJO-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150271#comment-14150271
]
ASF GitHub Bot commented on TAJO-962:
-------------------------------------
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/164
TAJO-962: Column reference used in LIMIT clause incurs NPE.
It fixed the bug and adds the unit test system for PreLogicalPlanVerifier.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-962
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/164.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 #164
----
commit d1557a6032ef86fd75a82119e1c0728197f31baf
Author: Hyunsik Choi <[email protected]>
Date: 2014-09-27T00:00:04Z
TAJO-962: Column reference used in LIMIT clause incurs NPE.
----
> Column reference used in LIMIT clause incurs NPE.
> -------------------------------------------------
>
> Key: TAJO-962
> URL: https://issues.apache.org/jira/browse/TAJO-962
> Project: Tajo
> Issue Type: Bug
> Components: planner/optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Priority: Trivial
> Fix For: 0.9.0
>
>
> {noformat}
> select * from LINEITEM limit L_ORDERKEY;
> {noformat}
> Of course, any column reference is not allowed in LIMIT clause. But, the
> above query will cause NPE. This is an query validator bug.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
