[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-310?pag...
]
Sanne Grinovero commented on HSEARCH-310:
-----------------------------------------
I was trying the new solution, I got blocked again at the point I need to check the
object(s) I'm returning from the cache are still managed.
What we cache is actually a Object[] and it is possible for it to contain projected
Strings, which are going to return false to the is-attached-to-session test, having me
reload the data in all cases; so cache is useless when there are projected fields.
Going to think about it... ignore the case? open another issue about returning unattached
objects? We probably need to change DocumentExtractor so that I can ask for which
positions in the array are expected to be managed.
Out of Memory on ScrollableResults
----------------------------------
Key: HSEARCH-310
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-310
Project: Hibernate Search
Issue Type: Bug
Components: query
Affects Versions: 3.0.1.GA
Environment: Java SE, 3.0.1.GA
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Fix For: 3.1.1
http://forum.hibernate.org/viewtopic.php?p=2400452
I think this is more appropriate for 3.1.1
Emmanuel said:
"The implementation suffers several flows:
- we do create an EntityInfo[] as big as the number of hits
- we lazily load this array but we never release "old content"
- we lazily load the content (ie objects) by window but we never release it
Some Soft reference based cache can help."
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira