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

Michael McCandless commented on LUCENE-1749:
--------------------------------------------

{quote}
Asking the searcher for the docFreq is the right thing to do... but people who 
rely on Weight being serializable might be in for a nasty surprise.
{quote}

Argh, right.

bq. If we decide not to ask weight to hang onto it's searcher, then the other 
way to do it right is to change explain() to accept a Searcher as well as a 
IndexReader.

+1

bq. Of course... one might wonder if we should bother supporting serializable 
in Lucene longer term at all - anyone dealing with distributed systems has 
found it to have too many shortcomings anyway.

Yeah this was never really "settled" in LUCENE-1473.  Lucene currently
supports live serialization, but not cross-version
serialization... and we have moved RemoteSearchable to contrib and
removed RMI from Searchable.

Does Solr ever rely on Lucene's "implements Serializable"?


> 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-hossfork.patch, LUCENE-1749.patch, LUCENE-1749.patch, 
> LUCENE-1749.patch, LUCENE-1749.patch, LUCENE-1749.patch, LUCENE-1749.patch, 
> LUCENE-1749.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