[hibernate-issues] [Hibernate-JIRA] Resolved: (HSEARCH-531) Use Lucene fieldcache
Sanne Grinovero (JIRA)
noreply at atlassian.com
Mon Mar 7 10:32:08 EST 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanne Grinovero resolved HSEARCH-531.
-------------------------------------
Resolution: Fixed
> Use Lucene fieldcache
> ---------------------
>
> Key: HSEARCH-531
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-531
> Project: Hibernate Search
> Issue Type: Improvement
> Components: query
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Fix For: 3.4.0.Alpha1
>
>
> The Lucene per-segment FieldCache should be used for strings we fetch from the index (Stored), by default as we do with classname and PK.
> It might be useful for people to be able to add more fields to this cache in case of projections usage.
> (It's purpose is to speed up this reading of stored info - being per segment it's not invalidated per new IndexReader but per changed segments).
> Likely need a switch to turn it off, as it could consume much memory.
--
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list