[KinoSearch] utf8 warnings/error

[Scott Beck]

Hi Marvin,

On 8/25/07, Marvin Humphrey <marvin at rectangular.com> wrote:
<snip>
> I believe that the code that's to blame is new to KS 0.20_04.
> 0.20_04 contains a refactoring of KinoSearch's external sorter to
> perform some of its own memory management, using some innovations
> recently uncovered by Lucene developer Michael McCandless as he
> implemented a variant of the KinoSearch merge model in Lucene.  This
> led to improved speed, but at the expense of increased complexity,
> and somewhere hidden in that complexity is a nasty little bug.
>

I removed the changes to the sorting and patched 0.20_03 with all the
other changes and I still see index corruption when deleting. I don't
know if it helps you to know this, but if I turn off optimize on the
finish() calls, I only loose 1 record instead of most of the index.
I'll continue to debug. If you figure it out please let me know.

Thanks,

Scott

_______________________________________________
KinoSearch mailing list
KinoSearch at rectangular.com
http://www.rectangular.com/mailman/listinfo/kinosearch