Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 41818 invoked from network); 29 Dec 2010 16:55:50 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 29 Dec 2010 16:55:50 -0000 Received: (qmail 51079 invoked by uid 500); 29 Dec 2010 16:55:48 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 50764 invoked by uid 500); 29 Dec 2010 16:55:45 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 50756 invoked by uid 99); 29 Dec 2010 16:55:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Dec 2010 16:55:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of softwarevisualization@gmail.com designates 209.85.214.48 as permitted sender) Received: from [209.85.214.48] (HELO mail-bw0-f48.google.com) (209.85.214.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Dec 2010 16:55:39 +0000 Received: by bwz8 with SMTP id 8so10548383bwz.35 for ; Wed, 29 Dec 2010 08:55:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:content-type; bh=6zA1w/liSHokvZWhnHgvQ6YtXE0hVqJgajaHEYx963E=; b=N7GFYUMReIYRv8IKCAtVKXK+XJC0j1+Hl3N4btoCXyOT8vafTmfpatdCGLnYd/ywx4 vkUuvWB/WamoAY7wzIMznKNeSJ/bXTdRxqAS+Dn4L1CL22nbylUOrzORLt/Lo2fMaLT1 iGRI9PtdeNmYqTgZvHKzzB5eD0eVDfi/f41rs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=n6dExR3auTqdCIjAsoBe+wx5dlMjOskpGKJoxyYNmV8RtFycJ3hpCxfUdJe1PryPqM A2Hvn9FJJXNi5tN9Ff5HqoFPV0iOZQD7FmBYTEJ17E8cVMYk5XaH5WCb0GH51SVeguiD ZfjNDBmcDsZWy9f2hRGyoiyCbLAafgr9v5JUM= MIME-Version: 1.0 Received: by 10.204.137.199 with SMTP id x7mr135933bkt.165.1293641717947; Wed, 29 Dec 2010 08:55:17 -0800 (PST) Received: by 10.204.65.81 with HTTP; Wed, 29 Dec 2010 08:55:17 -0800 (PST) Reply-To: softwarevisualization@gmail.com In-Reply-To: <1596394141-1293637049-cardhu_decombobulator_blackberry.rim.net-1951755217-@b15.c6.bise7.blackberry> References: <1596394141-1293637049-cardhu_decombobulator_blackberry.rim.net-1951755217-@b15.c6.bise7.blackberry> Date: Wed, 29 Dec 2010 11:55:17 -0500 Message-ID: Subject: Re: Using Lucene to search live, being-edited documents From: software visualization To: java-user@lucene.apache.org, adam.saltiel@gmail.com Content-Type: multipart/alternative; boundary=00151747c136109fc904988f6fc4 --00151747c136109fc904988f6fc4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I am writing a text editor and have to provide a certain search functionality . The use case is for single user. A single document is potentially very large and numerous such documents may be open and unflushed at any given time. Think many files of an IDE, except the files are larger. The user is free to change, say, variables names across documents which may be separate files opened simultaneously in a variety of tabs (say) and being edited with no guarantee that the user has flushed or saved any of it. On Wed, Dec 29, 2010 at 10:37 AM, wrote: > This is interesting. What are we driving at here? A single user? That > doesn't make sense to unless you want to flag certain things as they > construct the document. Or else why don't they know what is in their own > document? There must be other ways apart from Lucene. It seems to me you > want each line parsed as soon as entered and matched against some criteri= a. > I would look at plugins for Open Office first. Or any other text editor. = But > not sure you have given enough information. > Sent using BlackBerry=AE from Orange > > -----Original Message----- > From: "Sean" > Date: Wed, 29 Dec 2010 15:35:17 > To: java-user > Reply-To: java-user@lucene.apache.org > Subject: Re:Using Lucene to search live, being-edited documents > > Does it make any sense? > Every time a search result is shown, the original document could have be= en > changed, no matter how fast the indexing speed is. > If you can accept this inconsistency, you do not need to index so > frequently at all. > > > ------------------ Original ------------------ > From: "software visualization"; > Date: Wed, Dec 29, 2010 06:06 AM > To: "java-user"; > > Subject: Using Lucene to search live, being-edited documents > > > This has probably been asked before but I couldn't find it, so... > > Is it possible / advisable / practical to use Lucene as the basis of a > live > document search capability? By "live document" I mean a largish document > such as a word processor might be able to handle which is being edited > currently. Examples would be Word documents of some size that are begin > written, really huge Java files, etc. > > The user is sitting there typing away and of course everything is changin= g > in real time. This seems to be orthogonal to the idea of a Lucene index > which is costly to construct and costly to update. > > TIA > --00151747c136109fc904988f6fc4--