[ 
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736304#action_12736304
 ] 

Hoss Man commented on LUCENE-1749:
----------------------------------

Mark: i have a little time to work on this today ... do you have any updates 
that youv'e been working on locally (i noticed some patch add/retract from you 
in hte history)

Paul: over in LUCENE-831 there was a lot of discussion and work done towards 
making the entire FieldCAche internals pluggable so you could customize the 
cache behavior all sorts of ways ... i feel out of the loop on that issue, but 
my understanding is that it was pushed back to 3.1 at the earliest because it 
wasn't clear how the APIs should be setup given the work being done with reopen 
and with moving FieldCache usage down to the subreaders.

for now my goal with this issue (LUCENE-1749) is purely to provide an 
experimental  (ie: no back compat expectations) API for app developers to use 
to sanity check that the changes in 2.9 havne't blown their RAM usage sky high.

> FieldCache introspection API
> ----------------------------
>
>                 Key: LUCENE-1749
>                 URL: https://issues.apache.org/jira/browse/LUCENE-1749
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: Search
>            Reporter: Hoss Man
>            Priority: Minor
>             Fix For: 2.9
>
>         Attachments: fieldcache-introspection.patch, LUCENE-1749.patch, 
> LUCENE-1749.patch, LUCENE-1749.patch
>
>
> FieldCache should expose an Expert level API for runtime introspection of the 
> FieldCache to provide info about what is in the FieldCache at any given 
> moment.  We should also provide utility methods for sanity checking that the 
> FieldCache doesn't contain anything "odd"...
>    * entries for the same reader/field with different types/parsers
>    * entries for the same field/type/parser in a reader and it's subreader(s)
>    * etc...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org

Reply via email to