[jira] [Updated] (DRILL-2167) Order by on a repeated index from the output of a flatten on large no of records results in incorrect results

2015-06-30 Thread Jacques Nadeau (JIRA)

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

Jacques Nadeau updated DRILL-2167:
--
Fix Version/s: 1.1.0

 Order by on a repeated index from the output of a flatten on large no of 
 records results in incorrect results
 -

 Key: DRILL-2167
 URL: https://issues.apache.org/jira/browse/DRILL-2167
 Project: Apache Drill
  Issue Type: Bug
  Components: Execution - Relational Operators
Reporter: Rahul Challapalli
Assignee: Jason Altekruse
Priority: Critical
 Fix For: 1.1.0

 Attachments: data.json


 git.commit.id.abbrev=3e33880
 The below query results in 26 records. Based on the data set we should 
 only receive 20 records. 
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s 
 order by s.rms.rptd[1].d;
 {code}
 When I removed the order by part, drill correctly reported 20 records.
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s;
 {code}
 I attached the data set with 2 records. I copied over the data set 5 
 times and ran the queries on top of it. Let me know if you have any other 
 questions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (DRILL-2167) Order by on a repeated index from the output of a flatten on large no of records results in incorrect results

2015-05-08 Thread Victoria Markman (JIRA)

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

Victoria Markman updated DRILL-2167:

Fix Version/s: (was: 1.0.0)
   1.1.0

 Order by on a repeated index from the output of a flatten on large no of 
 records results in incorrect results
 -

 Key: DRILL-2167
 URL: https://issues.apache.org/jira/browse/DRILL-2167
 Project: Apache Drill
  Issue Type: Bug
  Components: Execution - Relational Operators
Reporter: Rahul Challapalli
Assignee: Jason Altekruse
Priority: Critical
 Fix For: 1.1.0

 Attachments: data.json


 git.commit.id.abbrev=3e33880
 The below query results in 26 records. Based on the data set we should 
 only receive 20 records. 
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s 
 order by s.rms.rptd[1].d;
 {code}
 When I removed the order by part, drill correctly reported 20 records.
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s;
 {code}
 I attached the data set with 2 records. I copied over the data set 5 
 times and ran the queries on top of it. Let me know if you have any other 
 questions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (DRILL-2167) Order by on a repeated index from the output of a flatten on large no of records results in incorrect results

2015-04-15 Thread Chris Westin (JIRA)

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

Chris Westin updated DRILL-2167:

Fix Version/s: (was: 0.9.0)
   1.0.0

 Order by on a repeated index from the output of a flatten on large no of 
 records results in incorrect results
 -

 Key: DRILL-2167
 URL: https://issues.apache.org/jira/browse/DRILL-2167
 Project: Apache Drill
  Issue Type: Bug
  Components: Execution - Relational Operators
Reporter: Rahul Challapalli
Assignee: Sudheesh Katkam
Priority: Critical
 Fix For: 1.0.0

 Attachments: data.json


 git.commit.id.abbrev=3e33880
 The below query results in 26 records. Based on the data set we should 
 only receive 20 records. 
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s 
 order by s.rms.rptd[1].d;
 {code}
 When I removed the order by part, drill correctly reported 20 records.
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s;
 {code}
 I attached the data set with 2 records. I copied over the data set 5 
 times and ran the queries on top of it. Let me know if you have any other 
 questions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (DRILL-2167) Order by on a repeated index from the output of a flatten on large no of records results in incorrect results

2015-02-23 Thread Chris Westin (JIRA)

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

Chris Westin updated DRILL-2167:

Fix Version/s: 0.9.0

 Order by on a repeated index from the output of a flatten on large no of 
 records results in incorrect results
 -

 Key: DRILL-2167
 URL: https://issues.apache.org/jira/browse/DRILL-2167
 Project: Apache Drill
  Issue Type: Bug
  Components: Execution - Relational Operators
Reporter: Rahul Challapalli
Assignee: Jason Altekruse
Priority: Critical
 Fix For: 0.9.0

 Attachments: data.json


 git.commit.id.abbrev=3e33880
 The below query results in 26 records. Based on the data set we should 
 only receive 20 records. 
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s 
 order by s.rms.rptd[1].d;
 {code}
 When I removed the order by part, drill correctly reported 20 records.
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s;
 {code}
 I attached the data set with 2 records. I copied over the data set 5 
 times and ran the queries on top of it. Let me know if you have any other 
 questions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (DRILL-2167) Order by on a repeated index from the output of a flatten on large no of records results in incorrect results

2015-02-22 Thread Jacques Nadeau (JIRA)

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

Jacques Nadeau updated DRILL-2167:
--
Component/s: Execution - Relational Operators

 Order by on a repeated index from the output of a flatten on large no of 
 records results in incorrect results
 -

 Key: DRILL-2167
 URL: https://issues.apache.org/jira/browse/DRILL-2167
 Project: Apache Drill
  Issue Type: Bug
  Components: Execution - Relational Operators
Reporter: Rahul Challapalli
Assignee: Jason Altekruse
Priority: Critical
 Attachments: data.json


 git.commit.id.abbrev=3e33880
 The below query results in 26 records. Based on the data set we should 
 only receive 20 records. 
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s 
 order by s.rms.rptd[1].d;
 {code}
 When I removed the order by part, drill correctly reported 20 records.
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s;
 {code}
 I attached the data set with 2 records. I copied over the data set 5 
 times and ran the queries on top of it. Let me know if you have any other 
 questions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (DRILL-2167) Order by on a repeated index from the output of a flatten on large no of records results in incorrect results

2015-02-04 Thread Rahul Challapalli (JIRA)

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

Rahul Challapalli updated DRILL-2167:
-
Attachment: data.json

 Order by on a repeated index from the output of a flatten on large no of 
 records results in incorrect results
 -

 Key: DRILL-2167
 URL: https://issues.apache.org/jira/browse/DRILL-2167
 Project: Apache Drill
  Issue Type: Bug
Reporter: Rahul Challapalli
Assignee: Jason Altekruse
Priority: Critical
 Attachments: data.json


 git.commit.id.abbrev=3e33880
 The below query results in 26 records. Based on the data set we should 
 only receive 20 records. 
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s 
 order by s.rms.rptd[1].d;
 {code}
 When I removed the order by part, drill correctly reported 20 records.
 {code}
 select s.uid from (select d.uid, flatten(d.map.rm) rms from `data.json` d) s;
 {code}
 I attached the data set with 2 records. I copied over the data set 5 
 times and ran the queries on top of it. Let me know if you have any other 
 questions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)