Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of jason.rutherglen@gmail.com
 designates 74.125.44.28 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=kFfUDcYNle8/I6msu3seZY0vz0poZIzfIDYPZ88uNUVgdWhRWxTTVI0BKZchTUqb08
         vuqdxWXynQ9MM5VbrVVEX2nqvGT2JeqGqb8dc58M1hE2TBrjCEfOwfCC7mOdFO23OMUX
         Xj/0c1n+o3VbKFHwYl7aD/7FRrCEOtX76SfC8=
MIME-Version: 1.0
Date: Wed, 1 Apr 2009 16:05:21 -0700
Message-ID: <85d3c3b60904011605l44cdf9d7k91df4f3ebd8a134d@mail.gmail.com>
Subject: Future projects
From: Jason Rutherglen <jason.rutherglen@gmail.com>
To: java-dev@lucene.apache.org
Content-Type: multipart/alternative; boundary=000e0cd4033296ccb8046686598e

--000e0cd4033296ccb8046686598e
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Now that LUCENE-1516 is close to being committed perhaps we can
figure out the priority of other issues:

1. Searchable IndexWriter RAM buffer

2. Finish up benchmarking and perhaps implement passing
filters to the SegmentReader level

3. Deleting by doc id using IndexWriter

With 1) I'm interested in how we will lock a section of the
bytes for use by a given reader? We would not actually lock
them, but we need to set aside the bytes such that for example
if the postings grows, TermDocs iteration does not progress to
beyond it's limits. Are there any modifications that are needed
of the RAM buffer format? How would the term table be stored? We
would not be using the current hash method?

--000e0cd4033296ccb8046686598e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Now that LUCENE-1516 is close to being committed perhaps we can<br>figure o=
ut the priority of other issues:<br><br>1. Searchable IndexWriter RAM buffe=
r <br><br>2. Finish up benchmarking and perhaps implement passing<br>filter=
s to the SegmentReader level <br>
<br>3. Deleting by doc id using IndexWriter<br><br>With 1) I&#39;m interest=
ed in how we will lock a section of the<br>bytes for use by a given reader?=
 We would not actually lock<br>them, but we need to set aside the bytes suc=
h that for example<br>
if the postings grows, TermDocs iteration does not progress to<br>beyond it=
&#39;s limits. Are there any modifications that are needed<br>of the RAM bu=
ffer format? How would the term table be stored? We<br>would not be using t=
he current hash method?<br>

--000e0cd4033296ccb8046686598e--