[jira] [Updated] (DRILL-6217) NaN/Inf: NestedLoopJoin processes NaN values incorrectly

2018-03-09 Thread Pritesh Maker (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DRILL-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pritesh Maker updated DRILL-6217:
-
Fix Version/s: (was: 1.14.0)
   1.13.0

> 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
>Affects Versions: 1.12.0
>Reporter: Volodymyr Tkach
>Assignee: Volodymyr Tkach
>Priority: Major
>  Labels: ready-to-commit
> Fix For: 1.13.0
>
> 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)

[jira] [Updated] (DRILL-6217) NaN/Inf: NestedLoopJoin processes NaN values incorrectly

2018-03-09 Thread Arina Ielchiieva (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DRILL-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arina Ielchiieva updated DRILL-6217:

Labels: ready-to-commit  (was: )

> 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
>Affects Versions: 1.12.0
>Reporter: Volodymyr Tkach
>Assignee: Volodymyr Tkach
>Priority: Major
>  Labels: ready-to-commit
> Fix For: 1.14.0
>
> 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)

[jira] [Updated] (DRILL-6217) NaN/Inf: NestedLoopJoin processes NaN values incorrectly

2018-03-08 Thread Pritesh Maker (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DRILL-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pritesh Maker updated DRILL-6217:
-
Fix Version/s: (was: 1.13.0)
   1.14.0

> 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
>Affects Versions: 1.12.0
>Reporter: Volodymyr Tkach
>Assignee: Volodymyr Tkach
>Priority: Major
> Fix For: 1.14.0
>
> 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)

[jira] [Updated] (DRILL-6217) NaN/Inf: NestedLoopJoin processes NaN values incorrectly

2018-03-07 Thread Arina Ielchiieva (JIRA) 

 [ 
https://issues.apache.org/jira/browse/DRILL-6217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arina Ielchiieva updated DRILL-6217:

Affects Version/s: 1.12.0
 Reviewer: Arina Ielchiieva
Fix Version/s: 1.13.0

> 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
>Affects Versions: 1.12.0
>Reporter: Volodymyr Tkach
>Assignee: Volodymyr Tkach
>Priority: Major
> Fix For: 1.13.0
>
> 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)