On Wed, Jun 25, 2008 at 11:30 AM, Jason Rutherglen <[EMAIL PROTECTED]> wrote: > I read other parts of the email but glanced over this part. Would terms be > automatically sorted as they came in? If implemented it would be nice to be > able to get an encoded representation (probably byte array) of the document > and postings which could be written to a log, and then reentered in another > IndexWriter recreating the document and postings.
I was talking simpler... If one could open an IndexReader on the index (including uncommitted documents in the open IndexWriter), then you can easily search for a document and retrieve it's stored fields in order to re-index it with changes (and still maintain decent performance). -Yonik > On Wed, Jun 25, 2008 at 8:41 AM, Yonik Seeley <[EMAIL PROTECTED]> wrote: >> >> On Wed, Jun 25, 2008 at 6:29 AM, Michael McCandless >> <[EMAIL PROTECTED]> wrote: >> > We've also discussed at one point creating an IndexReader impl that >> > searches >> > the RAM buffer that DocumentsWriter writes to when adding documents. I >> > think it's easier than it sounds, on first glance, because >> > DocumentsWriter >> > is in fact writing the postings in nearly the same format as is used >> > when >> > the segment is flushed. >> >> That would be very nice, and should also make it much easier to >> implement updateable documents (changing/adding/removing single >> fields). >> >> -Yonik >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
