[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1749:
-----------------------------
Attachment: LUCENE-1749.patch
More progress building on Mark's patch.
added some sanity checking that reader/fieldname combos aren't reused in odd
ways -- i made it ignore cases where different parsers ultimately resolve to
identical cache objects (ie null vs DEFAULT_LONG_PARSER) and it ignores any
CreationPlaceholder objects (not sure about that one)
some tests were modified to make their pathological behavior more "sane" and
hooks were addded so that future tests can bypass the sanity testing in the
tearDown method if they really need to.
Still need sanity testing of the Reader/subreader variety. also lots of docs
and code cleanup.
BTW: i was focused on test-core ... still waiting on test-contrib to finish
running, so i'm not yet sure if i broke anything there.
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
