[
https://issues.jboss.org/browse/TEIID-2601?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2601.
-----------------------------------
Fix Version/s: 8.4.1
8.5
Resolution: Done
Added logic to the logmanger/serialization of lobs to prevent operations that would render
a streaming lob invalid. Also improved the design of connectormanager.
Better handling for streamed lobs
---------------------------------
Key: TEIID-2601
URL:
https://issues.jboss.org/browse/TEIID-2601
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 8.2
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4.1, 8.5
When the ws translator returns a streamed result internal operations, such as adding to a
tuple buffer may attempt to obtain the length, etc. that render the lob unusable and
result in opaque errors, such as
"TEIID30035 Wrong type of data found or no data found; expecting streamable object
from the buffer manager"
We should make streaming best effort (such as resorting to the copy on read logic), more
fool-proof with internal operations, or at least improve the error message.
--
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