[
https://issues.apache.org/jira/browse/LUCENE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12487433
]
Otis Gospodnetic commented on LUCENE-857:
-----------------------------------------
I think this is where a javadoc and CHANGES.txt come in. People with serious
production environments don't just throw new Lucene version on top of the old
one without carefully reading CHANGES.txt. I do this every time I upgrade. If
one is careless and doesn't read that, then, well...
What you suggested is okay, but I didn't want to deprecate the whole class,
just remove the caching concern from it, as that's what the CWF is concerned
with already. With your suggestion one can't get a raw QueryFilter without
getting it automatically cached. Isn't this inflexibility uncool?
> Remove BitSet caching from QueryFilter
> --------------------------------------
>
> Key: LUCENE-857
> URL: https://issues.apache.org/jira/browse/LUCENE-857
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Otis Gospodnetic
> Assigned To: Otis Gospodnetic
> Priority: Minor
> Attachments: LUCENE-857.patch
>
>
> Since caching is built into the public BitSet bits(IndexReader reader)
> method, I don't see a way to deprecate that, which means I'll just cut it out
> and document it in CHANGES.txt. Anyone who wants QueryFilter caching will be
> able to get the caching back by wrapping the QueryFilter in the
> CachingWrapperFilter.
--
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]
