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

Steven Hawkins (JIRA) jira-events at lists.jboss.org
Tue Aug 21 22:45:14 EDT 2012


     [ https://issues.jboss.org/browse/TEIID-2153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins resolved TEIID-2153.
-----------------------------------

    Resolution: Done


Changed the code to allow cache entry lobs to be readable after close as the filestore will not be removed until all of the lobs are gc'd.

Also I'll treat more proactive lob cleanup as a separate issue.  We'll need to distinguish between persistent values created by processing (as opposed to cache/source values) and remove their stores only on the removal of the requestbuffer.  removal based upon intermediate buffers would result in invalid blobs unless we have better reference tracking.
                
> 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

        


More information about the teiid-issues mailing list