[
https://issues.apache.org/jira/browse/TAJO-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15149752#comment-15149752
]
ASF GitHub Bot commented on TAJO-2077:
--------------------------------------
GitHub user jinossy opened a pull request:
https://github.com/apache/tajo/pull/963
TAJO-2077: Join condition causes incorrect result, when a table has an
empty row file.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jinossy/tajo TAJO-2077
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/963.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 #963
----
commit 58b4cc249e5621b87edbf3f192f78d4443e63418
Author: Jinho Kim <[email protected]>
Date: 2016-02-17T02:51:13Z
TAJO-2077: Join condition causes incorrect result, when a table has an
empty row file.
----
> Join condition causes incorrect result, when a table has an empty row file
> --------------------------------------------------------------------------
>
> Key: TAJO-2077
> URL: https://issues.apache.org/jira/browse/TAJO-2077
> Project: Tajo
> Issue Type: Bug
> Components: Physical Operator
> Affects Versions: 0.10.0, 0.11.0
> Reporter: Jinho Kim
> Assignee: Jinho Kim
> Priority: Critical
> Fix For: 0.12.0, 0.11.2
>
>
> MergeScanner termination condition is null tuple. if file fragment is still
> exist and first fragment returns null tuple, other fragments is ignored.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
