[
https://jira.jboss.org/jira/browse/TEIID-771?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-771.
----------------------------------
Resolution: Done
Updated tuplesourceinfo to hold references to contained lobs and to track persistent
streams via their containing lob - when it's gc'ed then the tuplesource will be
removed (if not already removed by a connection close).
Simplify lob handling in the buffermanager
------------------------------------------
Key: TEIID-771
URL:
https://jira.jboss.org/jira/browse/TEIID-771
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 6.2.0
Lob handling in the buffermanager relies upon overloading the notion of tuple source
group and on reassigning the streamable obejcts to the latest tuple source / group.
However it's possible for the same streamable object to be associated with multiple
tuple sources. Callers should not be forced to handle invalidreferenceexceptions, since
implementors of udf, or even internal code, will fail without explicit handling.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira