[
https://issues.apache.org/jira/browse/LUCENE-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736310#action_12736310
]
Uwe Schindler commented on LUCENE-1764:
---------------------------------------
I think this bug was there before. SortField has the problem that not only
SortComparator, also custom parsers that are not singletons (serializable
singletons using readResolve()!!!) or do not have equals/hashcode will create
new cache entries each time, e.g. this one:
"new SortField("field", new FieldCache.LongParser() { ... });" creates a
different parser instance each time and so a new cache entry is created (even
in non-remote usage). This is noted in the docs.
> Remote Searching w/sort using SortComparator has explosive FieldCache usage
> ---------------------------------------------------------------------------
>
> Key: LUCENE-1764
> URL: https://issues.apache.org/jira/browse/LUCENE-1764
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Hoss Man
> Fix For: 2.9
>
>
> As discovered in LUCENE-1749, when using identical instances of a
> SortComparator you get multiple entries in the FieldCache.
> demonstrating this bug currently requires the patches in LUCENE-1749.
> See markmiller's comment here...
> https://issues.apache.org/jira/browse/LUCENE-1749?focusedCommentId=12735190#action_12735190
--
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
