[
https://issues.apache.org/jira/browse/LUCENE-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12767541#action_12767541
]
Aaron McKee commented on LUCENE-1995:
-
I make no claims to the reasonablenes
: Search
Affects Versions: 2.9
Reporter: Aaron McKee
Priority: Minor
re: FilterManager.getFilter(Filter filter)
FilterManager is using the filter's hash code as the key to its filter cache,
however hash codes are intrinsically not guaranteed to be distinct; diff
In the code I'm working with, I generate a cache of calculated values as
a by-product within a Filter.getDocidSet implementation (and within a
Query-ized version of the filter and its Scorer method) . These values
are keyed off the IndexReader's docID values, since that's all that's
accessibl
This all sounds like great work, thank you for putting in the time! I
ended up retooling a fair bit of Spatial myself (especially the Tiering
stuff which was, perhaps, a bit questionable in places). One of the
bigger concerns I had throughout the package, after delving into it, was
the overus
ading). If I were to begin development on a few things (such as
the above, if it hasn't already been done/slated), would I just fall
hopelessly out-of-sync in short order?
Thank you for your time and insight!
Best Regards,
A