[JBoss JIRA] (TEIID-2153) Allow LOBs to be accessable after the statement close in the local connection scenarios
11:53 a.m.
Ramesh Reddy created TEIID-2153:
-----------------------------------
Summary: 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
1:07 p.m.
[
https://issues.jboss.org/browse/TEIID-2153?page=com.atlassian.jira.plugin...
]
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
9:41 a.m.
[
https://issues.jboss.org/browse/TEIID-2153?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2153:
-------------------------------------
I think if we just do the lob cleanup is fine. Caching can be separate issue.
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
9:45 p.m.
[
https://issues.jboss.org/browse/TEIID-2153?page=com.atlassian.jira.plugin...
]
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
8:06 a.m.
[
https://issues.jboss.org/browse/TEIID-2153?page=com.atlassian.jira.plugin...
]
Steven Hawkins closed TEIID-2153.
---------------------------------
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
4494
days inactive
4586
days old
4 comments
2 participants
participants (2)
-
Ramesh Reddy (JIRA) -
Steven Hawkins (JIRA)