[
https://issues.jboss.org/browse/TEIID-3050?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-3050.
-----------------------------------
Resolution: Done
Changed the logic to be aware of whether there is an existing transaction or no txn needed
to not perform full buffering. Also in the non-txn scenarios for batch/iterator we'll
not perform read/write with some concurrency.
allow for more incremental insert with iterator
-----------------------------------------------
Key: TEIID-3050
URL:
https://issues.jboss.org/browse/TEIID-3050
Project: Teiid
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Misc. Connectors, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.9
The current bulk insert logic assumes that it is avoiding a global transactions by fully
reading the results before sending the tuplebuffer iterator to the source for processing,
which can then just use a local transaction. However if we are already operating under a
transaction or the user doesn't want a transaction (such as with a staging
materialized view load) then the insert should happen more incrementally.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)