[ https://issues.apache.org/jira/browse/LUCENE-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079771#comment-13079771 ]
Hoss Man commented on LUCENE-3360: ---------------------------------- See also... * LUCENE-831 - the first issue (i know of) to discuss flipping the relationship between FieldCache and IndexReader (but got hung up on other things, particularly how reopen would affect this) * LUCENE-1785 - where thought was put into how to merge FieldCaches when Segments are merged * LUCENE-2665 - where a lot of work was already done to think about the "right" FieldCache API > Move FieldCache to IndexReader > ------------------------------ > > Key: LUCENE-3360 > URL: https://issues.apache.org/jira/browse/LUCENE-3360 > Project: Lucene - Java > Issue Type: Improvement > Reporter: Martijn van Groningen > Fix For: 3.4, 4.0 > > Attachments: LUCENE-3360.patch > > > Move the static FieldCache.DEFAULT field instance to atomic IndexReaders, so > that FieldCache insanity caused by the WeakHashMap no longer occurs. > * Add a new method to IndexReader that by default throws an UOE: > {code}public FieldCache getFieldCache(){code} > * The SegmentReader implements this method and returns its own internal > FieldCache implementation. This implementation just uses a > HashMap<Entry<T>,Object>> to store entries. > * The SlowMultiReaderWrapper implements this method as well and basically > behaves the same as the current FieldCacheImpl. > This issue won't solve the insanity that comes from inconsistent usage of a > single field (for example retrieve both int[] and DocTermIndex for the same > field). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org