[ http://issues.apache.org/jira/browse/LUCENE-731?page=comments#action_12453786 ] benson margulies commented on LUCENE-731: -----------------------------------------
Which means that I have to constantly close and recreate the searcher, as well? How is this 'simultaneous' .. ok, I see, you can search for what was stored up until the last call to close(). Gosh, it would be nice if there were a communications mechanism so that a call to 'commit' on a writer just caused extant searchers to catch up. And what if the index is so large that the searcher can't have loaded it entirely into memory? At very least, a flush() that saved recreation would seem helpful. Is the pattern to create searchers with short lifetimes? That seems like an expensive proposition. > Simple attempt at adding and searching at the same time fails. > -------------------------------------------------------------- > > Key: LUCENE-731 > URL: http://issues.apache.org/jira/browse/LUCENE-731 > Project: Lucene - Java > Issue Type: Bug > Components: Index > Affects Versions: 2.0.0 > Environment: Windows XP, java 1.4. > Reporter: benson margulies > Attachments: LuceneBooleanQuery.java > > > The FAQ says that you can index and lookup simultaneously. I tried what > appeared to be the simplest possible implementation of that, and the searcher > never finds anything. I will attach a junit test. > If the code is working as designed, please consider this a bug in the FAQ or > some other doc that there is no pattern given for how to do this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
