To actually obtain an IndexSearcher from NRTManager, it's a 2-step process now.
You must .getSearcherManager(), then .acquire() from the returned SearcherManager.
This is very trappy... because if the app incorrectly calls maybeReopen on that private SearcherManager (instead of NRTManager.maybeReopen) then it can unexpectedly cause threads to block forever, waiting for the necessary gen to become visible. This will be hard to debug... I don't like creating trappy APIs.
LUCENE-3761 is in, we can fix NRTManager to no longer expose its private SM, instead subclassing ReferenceManaager.
Or alternatively, or in addition, maybe we factor out a new interface (SearcherProvider or something...) that only has acquire and release methods, and both NRTManager and ReferenceManager/SM impl that, and we keep NRTManager's SM private.
|Field||Original Value||New Value|
|Assignee||Michael McCandless [ mikemccand ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|3d 23h 45m||1||Michael McCandless||17/Feb/12 19:30|
|447d 15h 13m||1||Uwe Schindler||10/May/13 11:44|