KS/Ferret merging of stored fields and term vectors

Hey, Dave... I know some of the merging optimizations in
ferret are  
enabled by fixed field numbers... I just switched over the
KS index  
format to key both stored fields and term vectors off of
field names  
rather than field numbers, and now there's *never* a need to
remap --  
KS can always read the record as one chunk and transfer it
to the new  
segment without knowing anything about it.

Sure, there's a small space penalty, but it was nice to
chuck that  
resolving code. 

Marvin Humphrey
Rectangular Research
http://www.rectangular.co
m/

On 3/3/07, Marvin Humphrey <marvinrectangular.com> wrote:
> Hey, Dave... I know some of the merging optimizations
in ferret are
> enabled by fixed field numbers... I just switched over
the KS index
> format to key both stored fields and term vectors off
of field names
> rather than field numbers, and now there's *never* a
need to remap --
> KS can always read the record as one chunk and transfer
it to the new
> segment without knowing anything about it.
>
> Sure, there's a small space penalty, but it was nice to
chuck that
> resolving code. 

Damn, why didn't I think of that. Nice idea.

-- 
Dave Balmain
http://www.davebalmain.co
m/