Return-Path: Delivered-To: apmail-lucene-java-dev-archive@www.apache.org Received: (qmail 78382 invoked from network); 28 Nov 2006 03:32:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Nov 2006 03:32:45 -0000 Received: (qmail 85324 invoked by uid 500); 28 Nov 2006 03:32:52 -0000 Delivered-To: apmail-lucene-java-dev-archive@lucene.apache.org Received: (qmail 85277 invoked by uid 500); 28 Nov 2006 03:32:52 -0000 Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-dev@lucene.apache.org Delivered-To: mailing list java-dev@lucene.apache.org Received: (qmail 85266 invoked by uid 99); 28 Nov 2006 03:32:52 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Nov 2006 19:32:52 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Nov 2006 19:32:42 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3A2217142E4 for ; Mon, 27 Nov 2006 19:32:22 -0800 (PST) Message-ID: <30515170.1164684742208.JavaMail.jira@brutus> Date: Mon, 27 Nov 2006 19:32:22 -0800 (PST) From: "benson margulies (JIRA)" To: java-dev@lucene.apache.org Subject: [jira] Commented: (LUCENE-731) Simple attempt at adding and searching at the same time fails. In-Reply-To: <4276259.1164683601099.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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: java-dev-unsubscribe@lucene.apache.org For additional commands, e-mail: java-dev-help@lucene.apache.org