Daniel Noll is seeing an exception like this:
The class of our own is just an intermediary which delays creating the Filter object...
Tracing through the code in CachingWrapperFilter, I can see that this NPE would occur if getDocIdSet() were to return null.
The Javadoc on Filter says that null will be returned if no documents will be accepted by the filter, but it doesn't seem that Lucene itself is handling null return values correctly, so which is correct? The code or the Javadoc? Supposing that null really is OK, does this cause any problems with how CachingWrapperFilter is implementing the caching? I notice it's calling get() and then comparing against null so it wouldn't appear that it can distinguish "the entry isn't in the cache" from "the entry is in the cache but it's null".
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Workflow||jira [ 12511821 ]||Default workflow, editable Closed status [ 12564259 ]|
|Workflow||Default workflow, editable Closed status [ 12564259 ]||jira [ 12584081 ]|