You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by "Volodymyr Tkach (JIRA)" <ji...@apache.org> on 2018/03/07 08:43:00 UTC
[jira] [Created] (DRILL-6217) NaN/Inf: NestedLoopJoin processes NaN
values incorrectly
Volodymyr Tkach created DRILL-6217:
--------------------------------------
Summary: NaN/Inf: NestedLoopJoin processes NaN values incorrectly
Key: DRILL-6217
URL: https://issues.apache.org/jira/browse/DRILL-6217
Project: Apache Drill
Issue Type: Bug
Reporter: Volodymyr Tkach
Assignee: Volodymyr Tkach
Attachments: ObjsX.json
*AFFECTED_FUNCTIONALITY:* INNER JOIN (nestedloopjoin)
*ISSUE_DESCRIPTION:* according to *nestedloopjoin* query result NaN != NaN, however hashjoin / mergejoin behaves another way - NaN = NaN. As far as I understand, nestedloopjoin should behave like hashjoin / mergejoin. *STEPS*:
- Upload the attached file to Hadoop fs (ObjsX.json);
- Setup the following system settings:
*set planner.enable_nljoin_for_scalar_only = false*
*set planner.enable_hashjoin = false*
*set planner.enable_mergejoin = false*
*set planner.enable_nestedloopjoin = true*
- Run the following sql query {code} select distinct t.name from dfs.tmp.`ObjsX.json` t inner join dfs.tmp.`ObjsX.json` tt on t.attr4 = tt.attr4 {code}
*EXPECTED_RESULT:* It was expected to get the following result:
{code}
object1
object2
object3
object4
{code}
*ACTUAL_RESULT:* The actual result is:
{code}
object2
object3
object4
{code}
Please investigate and fix
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)