[
https://issues.jboss.org/browse/TEIID-5121?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-5121.
-----------------------------------
Fix Version/s: 8.12.x-6.4
Resolution: Done
Changed the tuple source sharing logic to pass a new parameter to the request, which will
direct the connector layer to create a copy of streaming lobs similar to when copyLobs is
enabled.
Streaming lob exception with shared tuple source
------------------------------------------------
Key: TEIID-5121
URL:
https://issues.jboss.org/browse/TEIID-5121
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.x-6.4
Reporter: Mario Majernik
Assignee: Steven Hawkins
Fix For: 10.0, 8.12.x-6.4
If a source returns streaming lobs and a shared tuple source is used, then a streaming
exception can occur when the tuple source is reused.
For example in TEIID-5093 a union of two identical branches of the same texttable will
result in the exception:
TEIID60019 Streaming result has already been read once.
This issue was separated from the S3 issue as it affects any streaming lob, which would
typically be from the ws translator/resource adapter.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)