[teiid-issues] [JBoss JIRA] (TEIID-2153) Allow LOBs to be accessable after the statement close in the local connection scenarios

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712540#comment-12712540 ] 

Steven Hawkins commented on TEIID-2153:
---------------------------------------

I hadn't thought about this in a while.  Also I think some of the initial work was done in the rest stuff using a remote connection to simplify development.  However, if using a local connection, then this already works for inlined or buffer backed lob values.  This is because we are not taking any explicit action on close/TupleBuffer removal to destroy the lob entries.  You can also tell sources to copy lobs, which will create an engine backed value.  

Non-inlined cache backed lob values can be problematic as the shared filestore cleanup is based upon the cache entry batchmanager getting garbage collected.

So a couple of things could be done.  We can address the last case of a non-inlined cache backed lob value and could be more proactive about lob cleanup in non-local connections.
                
> Allow LOBs to be accessable after the statement close in the local connection scenarios
> ---------------------------------------------------------------------------------------
>
>                 Key: TEIID-2153
>                 URL: https://issues.jboss.org/browse/TEIID-2153
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Query Engine
>    Affects Versions: 8.0
>            Reporter: Ramesh Reddy
>            Assignee: Steven Hawkins
>             Fix For: 8.2
>
>
> When a LOB returned the resultset, the contents of it are only accessed when resultset/statement and/or connection object is not closed, so that internal resources can be appropriately cleaned up. 
> This can be relaxed in the local connection scenarios, as the data access is occurring in the same VM, by taking advantage of single read nature of SQL/XML to cleanup once the resource is read or closed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira