3:05 p.m.
Steven Hawkins created TEIID-2098:
-------------------------------------
Summary: Caching does not interact well with Statement.setMaxRows
Key: TEIID-2098
URL: https://issues.jboss.org/browse/TEIID-2098
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
Most of the time setting maxRows will cause the plan to not be cachable and the results
will be cached/reused regardless of what subsequent maxRows are set to.
Finally a general issue is that if the query cannot have maxRows set as a limit (if there
is already a limit or it's a procedure call) then the maxRows is ignored.
--
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
1:13 p.m.
[
https://issues.jboss.org/browse/TEIID-2098?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2098:
---------------------------------------
Modified the preparedplan logic to add a limit to the command. Also added the ability to
get the final buffer from more nodes and tunneled the affect of setting the max rows.
Still need to handle cached result sets.
Caching does not interact well with Statement.setMaxRows
--------------------------------------------------------
Key: TEIID-2098
URL: https://issues.jboss.org/browse/TEIID-2098
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
Most of the time setting maxRows will cause the plan to not be cachable and the results
will be cached/reused regardless of what subsequent maxRows are set to.
Finally a general issue is that if the query cannot have maxRows set as a limit (if there
is already a limit or it's a procedure call) then the maxRows is ignored.
--
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
1:26 p.m.
[
https://issues.jboss.org/browse/TEIID-2098?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2098:
----------------------------------
It will need to be a KI that Statement.setMaxRows does not affect callablestatements that
return out/inout/return parameters.
Caching does not interact well with Statement.setMaxRows
--------------------------------------------------------
Key: TEIID-2098
URL: https://issues.jboss.org/browse/TEIID-2098
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
Most of the time setting maxRows will cause the plan to not be cachable and the results
will be cached/reused regardless of what subsequent maxRows are set to.
Finally a general issue is that if the query cannot have maxRows set as a limit (if there
is already a limit or it's a procedure call) then the maxRows is ignored.
--
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
8:06 a.m.
[
https://issues.jboss.org/browse/TEIID-2098?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2098.
-----------------------------------
Resolution: Done
Added a rowLimit field to the cache results so that if more results are requested and an
incomplete result is found, it will not be used. This could also be used to populate
partial cache entries when the entire result is not read, but that was not added.
Caching does not interact well with Statement.setMaxRows
--------------------------------------------------------
Key: TEIID-2098
URL: https://issues.jboss.org/browse/TEIID-2098
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
Most of the time setting maxRows will cause the plan to not be cachable and the results
will be cached/reused regardless of what subsequent maxRows are set to.
Finally a general issue is that if the query cannot have maxRows set as a limit (if there
is already a limit or it's a procedure call) then the maxRows is ignored.
--
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
8:09 a.m.
[
https://issues.jboss.org/browse/TEIID-2098?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2098:
----------------------------------
Issue Type: Bug (was: Feature Request)
I should add that the workaround for invalid cache results with older releases is not to
use setMaxRows when using result set caching.
Caching does not interact well with Statement.setMaxRows
--------------------------------------------------------
Key: TEIID-2098
URL: https://issues.jboss.org/browse/TEIID-2098
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
Most of the time setting maxRows will cause the plan to not be cachable and the results
will be cached/reused regardless of what subsequent maxRows are set to.
Finally a general issue is that if the query cannot have maxRows set as a limit (if there
is already a limit or it's a procedure call) then the maxRows is ignored.
--
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
7:42 a.m.
[
https://issues.jboss.org/browse/TEIID-2098?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-2098.
---------------------------------
Caching does not interact well with Statement.setMaxRows
--------------------------------------------------------
Key: TEIID-2098
URL: https://issues.jboss.org/browse/TEIID-2098
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.1
Most of the time setting maxRows will cause the plan to not be cachable and the results
will be cached/reused regardless of what subsequent maxRows are set to.
Finally a general issue is that if the query cannot have maxRows set as a limit (if there
is already a limit or it's a procedure call) then the maxRows is ignored.
--
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
4982
days inactive
5017
days old
5 comments
1 participants
participants (1)
-
Steven Hawkins (JIRA)