7:25 p.m.
Limit not working as expected
-----------------------------
Key: TEIID-1681
URL: https://issues.jboss.org/browse/TEIID-1681
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.3
Reporter: Gaurav Chaudhary
Assignee: Steven Hawkins
select CHORUS_B."ID", CHORUS_B."ACCESS_MODE",
CHORUS_B."USER_ID", CHORUS_B."CREATED_ON",
CHORUS_B."NOTE",'chorusdata.note' as "__objecttype__" from
(select * from chorus_notes.RETRIEVE_NOTES where
OBJECT_PKEY =
xmlserialize(xmlelement("demodata.rule", XMLATTRIBUTES(cast('name 1' as
String) as "name",cast('sysid 0' as String) as
"system",cast('user 1000' as String) as "user")) as String))
as CHORUS_B LIMIT 50
This query is not returning correct results unless we remove Limit from this.
If we include Limit over here, it interchanges the columns and returning incorrect data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:09 p.m.
New subject: [JBoss JIRA] Commented: (TEIID-1681) Limit not working as expected
[
https://issues.jboss.org/browse/TEIID-1681?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1681:
---------------------------------------
Can you attach the invalid query plan?
Limit not working as expected
-----------------------------
Key: TEIID-1681
URL: https://issues.jboss.org/browse/TEIID-1681
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.3
Reporter: Gaurav Chaudhary
Assignee: Steven Hawkins
Labels: Limit
select CHORUS_B."ID", CHORUS_B."ACCESS_MODE",
CHORUS_B."USER_ID", CHORUS_B."CREATED_ON",
CHORUS_B."NOTE",'chorusdata.note' as "__objecttype__" from
(select * from chorus_notes.RETRIEVE_NOTES where
OBJECT_PKEY =
xmlserialize(xmlelement("demodata.rule", XMLATTRIBUTES(cast('name 1' as
String) as "name",cast('sysid 0' as String) as
"system",cast('user 1000' as String) as "user")) as String))
as CHORUS_B LIMIT 50
This query is not returning correct results unless we remove Limit from this.
If we include Limit over here, it interchanges the columns and returning incorrect data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:14 a.m.
New subject: [JBoss JIRA] Commented: (TEIID-1681) Limit not working as expected
[
https://issues.jboss.org/browse/TEIID-1681?page=com.atlassian.jira.plugin...
]
Gaurav Chaudhary commented on TEIID-1681:
-----------------------------------------
ProjectNode
+ Output Columns:
0: ID (long)
1: ACCESS_MODE (string)
2: USER_ID (string)
3: CREATED_ON (string)
4: NOTE (string)
5: __objecttype__ (string)
+ Statistics:
0: Node Output Rows: 2
1: Node Process Time: 1
2: Node Cumulative Process Time: 7060
3: Node Cumulative Next Batch Process Time: 1
4: Node Next Batch Calls: 2
5: Node Blocks: 1
+ Cost Estimates:Estimated Node Cardinality: 50.0
+ Child 0:
ProjectNode
+ Output Columns:
0: ID (long)
1: ACCESS_MODE (string)
2: USER_ID (string)
3: CREATED_ON (string)
4: NOTE (string)
+ Statistics:
0: Node Output Rows: 2
1: Node Process Time: 0
2: Node Cumulative Process Time: 7059
3: Node Cumulative Next Batch Process Time: 0
4: Node Next Batch Calls: 2
5: Node Blocks: 1
+ Cost Estimates:Estimated Node Cardinality: 50.0
+ Child 0:
ProjectNode
+ Output Columns:
0: ID (long)
1: ACCESS_MODE (string)
2: USER_ID (string)
3: CREATED_ON (string)
4: NOTE (string)
+ Statistics:
0: Node Output Rows: 2
1: Node Process Time: 0
2: Node Cumulative Process Time: 7059
3: Node Cumulative Next Batch Process Time: 0
4: Node Next Batch Calls: 2
5: Node Blocks: 1
+ Cost Estimates:Estimated Node Cardinality: 50.0
+ Child 0:
LimitNode
+ Output Columns:
0: ID (long)
1: ACCESS_MODE (string)
2: USER_ID (string)
3: CREATED_ON (string)
4: NOTE (string)
+ Statistics:
0: Node Output Rows: 2
1: Node Process Time: 0
2: Node Cumulative Process Time: 7059
3: Node Cumulative Next Batch Process Time: 0
4: Node Next Batch Calls: 2
5: Node Blocks: 1
+ Cost Estimates:Estimated Node Cardinality: 50.0
+ Child 0:
DependentProcedureAccessNode
+ Output Columns:
0: ID (long)
1: NOTE (string)
2: USER_ID (string)
3: NOTES_TYPE (string)
4: ACCESS_MODE (string)
5: CREATED_ON (string)
+ Statistics:
0: Node Output Rows: 2
1: Node Process Time: 7059
2: Node Cumulative Process Time: 7059
3: Node Cumulative Next Batch Process Time: 0
4: Node Next Batch Calls: 2
5: Node Blocks: 1
+ Cost Estimates:Estimated Node Cardinality: -1.0
+ Query:EXEC
chorus_notes.RETRIEVE_NOTES(chorus_notes.RETRIEVE_NOTES.OBJECT_PKEY)
+ Model Name:chorus_notes
+ Row Offset:null
+ Row Limit:50
+ Select Columns:
0: ID
1: ACCESS_MODE
2: USER_ID
3: CREATED_ON
4: NOTE
+ Select Columns:
0: X.ID
1: X.ACCESS_MODE
2: X.USER_ID
3: X.CREATED_ON
4: X.NOTE
+ Select Columns:
0: CHORUS_NOTES.RETRIEVE_NOTES.ID
1: CHORUS_NOTES.RETRIEVE_NOTES.ACCESS_MODE
2: CHORUS_NOTES.RETRIEVE_NOTES.USER_ID
3: CHORUS_NOTES.RETRIEVE_NOTES.CREATED_ON
4: CHORUS_NOTES.RETRIEVE_NOTES.NOTE
5: 'chorusdata.note' AS "__objecttype__"
Limit not working as expected
-----------------------------
Key: TEIID-1681
URL: https://issues.jboss.org/browse/TEIID-1681
Project: Teiid
Issue Type: Bug
Components: JDBC Driver
Affects Versions: 7.3
Reporter: Gaurav Chaudhary
Assignee: Steven Hawkins
Labels: Limit
select CHORUS_B."ID", CHORUS_B."ACCESS_MODE",
CHORUS_B."USER_ID", CHORUS_B."CREATED_ON",
CHORUS_B."NOTE",'chorusdata.note' as "__objecttype__" from
(select * from chorus_notes.RETRIEVE_NOTES where
OBJECT_PKEY =
xmlserialize(xmlelement("demodata.rule", XMLATTRIBUTES(cast('name 1' as
String) as "name",cast('sysid 0' as String) as
"system",cast('user 1000' as String) as "user")) as String))
as CHORUS_B LIMIT 50
This query is not returning correct results unless we remove Limit from this.
If we include Limit over here, it interchanges the columns and returning incorrect data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:41 p.m.
New subject: [JBoss JIRA] Updated: (TEIID-1681) Limit not working as expected
[
https://issues.jboss.org/browse/TEIID-1681?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1681:
----------------------------------
Fix Version/s: 7.4.1
Component/s: Query Engine
(was: JDBC Driver)
Limit not working as expected
-----------------------------
Key: TEIID-1681
URL: https://issues.jboss.org/browse/TEIID-1681
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Reporter: Gaurav Chaudhary
Assignee: Steven Hawkins
Labels: Limit
Fix For: 7.4.1
select CHORUS_B."ID", CHORUS_B."ACCESS_MODE",
CHORUS_B."USER_ID", CHORUS_B."CREATED_ON",
CHORUS_B."NOTE",'chorusdata.note' as "__objecttype__" from
(select * from chorus_notes.RETRIEVE_NOTES where
OBJECT_PKEY =
xmlserialize(xmlelement("demodata.rule", XMLATTRIBUTES(cast('name 1' as
String) as "name",cast('sysid 0' as String) as
"system",cast('user 1000' as String) as "user")) as String))
as CHORUS_B LIMIT 50
This query is not returning correct results unless we remove Limit from this.
If we include Limit over here, it interchanges the columns and returning incorrect data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:41 p.m.
New subject: [JBoss JIRA] Resolved: (TEIID-1681) Limit not working as expected
[
https://issues.jboss.org/browse/TEIID-1681?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-1681.
-----------------------------------
Resolution: Done
Thanks for catching this Gaurav. The limit node was being pushed too far, which caused
the projection logic to not correctly get the output elements.
Limit not working as expected
-----------------------------
Key: TEIID-1681
URL: https://issues.jboss.org/browse/TEIID-1681
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Reporter: Gaurav Chaudhary
Assignee: Steven Hawkins
Labels: Limit
Fix For: 7.4.1
select CHORUS_B."ID", CHORUS_B."ACCESS_MODE",
CHORUS_B."USER_ID", CHORUS_B."CREATED_ON",
CHORUS_B."NOTE",'chorusdata.note' as "__objecttype__" from
(select * from chorus_notes.RETRIEVE_NOTES where
OBJECT_PKEY =
xmlserialize(xmlelement("demodata.rule", XMLATTRIBUTES(cast('name 1' as
String) as "name",cast('sysid 0' as String) as
"system",cast('user 1000' as String) as "user")) as String))
as CHORUS_B LIMIT 50
This query is not returning correct results unless we remove Limit from this.
If we include Limit over here, it interchanges the columns and returning incorrect data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:43 p.m.
New subject: [JBoss JIRA] Updated: (TEIID-1681) Limit not working as expected
[
https://issues.jboss.org/browse/TEIID-1681?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-1681:
----------------------------------
Fix Version/s: 7.5
Limit not working as expected
-----------------------------
Key: TEIID-1681
URL: https://issues.jboss.org/browse/TEIID-1681
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Reporter: Gaurav Chaudhary
Assignee: Steven Hawkins
Labels: Limit
Fix For: 7.4.1, 7.5
select CHORUS_B."ID", CHORUS_B."ACCESS_MODE",
CHORUS_B."USER_ID", CHORUS_B."CREATED_ON",
CHORUS_B."NOTE",'chorusdata.note' as "__objecttype__" from
(select * from chorus_notes.RETRIEVE_NOTES where
OBJECT_PKEY =
xmlserialize(xmlelement("demodata.rule", XMLATTRIBUTES(cast('name 1' as
String) as "name",cast('sysid 0' as String) as
"system",cast('user 1000' as String) as "user")) as String))
as CHORUS_B LIMIT 50
This query is not returning correct results unless we remove Limit from this.
If we include Limit over here, it interchanges the columns and returning incorrect data.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:54 p.m.
New subject: [JBoss JIRA] (TEIID-1681) Limit not working as expected
[
https://issues.jboss.org/browse/TEIID-1681?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-1681.
---------------------------------
Limit not working as expected
-----------------------------
Key: TEIID-1681
URL: https://issues.jboss.org/browse/TEIID-1681
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.3
Reporter: Gaurav Chaudhary
Assignee: Steven Hawkins
Labels: Limit
Fix For: 7.4.1, 7.5
select CHORUS_B."ID", CHORUS_B."ACCESS_MODE",
CHORUS_B."USER_ID", CHORUS_B."CREATED_ON",
CHORUS_B."NOTE",'chorusdata.note' as "__objecttype__" from
(select * from chorus_notes.RETRIEVE_NOTES where
OBJECT_PKEY =
xmlserialize(xmlelement("demodata.rule", XMLATTRIBUTES(cast('name 1' as
String) as "name",cast('sysid 0' as String) as
"system",cast('user 1000' as String) as "user")) as String))
as CHORUS_B LIMIT 50
This query is not returning correct results unless we remove Limit from this.
If we include Limit over here, it interchanges the columns and returning incorrect data.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4498
days inactive
4718
days old
6 comments
2 participants
participants (2)
-
Gaurav Chaudhary (JIRA) -
Steven Hawkins (JIRA)