[JBoss JIRA] (TEIID-2690) Tuples lost in a with clause item.
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2690?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-2690:
------------------------------------------------
Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1016243|https://bugzilla.redhat.com/show_bug.cgi?id=1016243] from ASSIGNED to MODIFIED
> Tuples lost in a with clause item.
> ----------------------------------
>
> Key: TEIID-2690
> URL: https://issues.jboss.org/browse/TEIID-2690
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.1, 7.7.7
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Blocker
> Fix For: 8.4.1, 8.6
>
>
> Related to TEIID-2442 - the BatchIterator created for the creation of the temp table backing a with clause item cannot be created after blocking without loosing tuples.
> On 8.3.x+ a single block is not sufficient to induce this behavior if there are any tuples that have been retrieved since the last block as the access node logic will return the partial batch. Thus may occur as a somewhat rare timing issue in 8.3.x+. However in 7.7.7/7.7.8 a single block cause the recreation of the BatchIterator making the affect almost certain once the row count exceeds the computed working batch size (nominally 256 rows, but allowed to vary based upon the row width).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-1226) Reuse dynamic sql plans and allow for prepared statements in procedure logic
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-1226?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-1226:
---------------------------------------
Ideally here we would reuse standard syntax, such as
PREPARE stmt FROM sql
EXECUTE stmt USING x, y, z
DEALLOCATE PREPARE stmt
This requires 2 new statements and a variation of our dynamic sql command.
Given our prepared infrastructure, it's just as easy though to have a single execute/prepare statement.
EXECUTE PREPARE stmt USING x, y, z
Here the context of the statement becomes important though as the plan should only be visible in the current/child procedure blocks.
> Reuse dynamic sql plans and allow for prepared statements in procedure logic
> ----------------------------------------------------------------------------
>
> Key: TEIID-1226
> URL: https://issues.jboss.org/browse/TEIID-1226
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 7.1
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Minor
> Fix For: 8.6
>
>
> Dynamic sql plans (for dynamic sql statements, lookup, and matview refreshes) should allow for plan reuse.
> Also procedure logic should have a mechanism to execute prepared statements for further plan reuse.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months