Hello Hoss,
On Jan 15, 2006, at 12:59 AM, Chris Hostetter wrote:
: IMO, there's no reason to allow field definitions to be spec'd more
: often than once per IndexWriter. Need to add a new field for docs
: 501-1000 of a 1000-doc indexing pass? No problem: create a new
: IndexWriter, define new fields, and you're off and running.
If I understand your argument, you are saying that the list of
fields and
their "flags" should be consistent in each segment -- and if
someone wants
to add new fields they should open a new IndexWriter so they get a new
segment.
So what happens when segments get merged?
Option 1: Merge field definitions at the segment level rather than
the Document level. The defs stay stored with individual segments,
but everything gets moved into the .fnm file, including
IS_COMPRESSED, IS_BINARY, etc (as I believe Robert was proposing).
Option 2: Centralize the field definitions; allow new fields
definitions to be added, but never allow modifications to individual
field definitions, just to the list. This is roughly analogous to
UPDATE TABLE in SQL, but more limited since you can't make arbitrary
changes.
I like option 1 better.
: Is it really necessary to be
: able to define new fields "at any time"?
Absafreakinglutely.
Down to the granularity of indexWriter.addDocument() ? Would it work
to open a new IndexWriter?
Marvin Humphrey
Rectangular Research
http://www.rectangular.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
