[KinoSearch] kinosearch 0.20 usable?
marvin at rectangular.com
Tue Feb 3 18:04:54 PST 2009
On Sun, Feb 01, 2009 at 11:20:35AM +0100, Gert Brinkmann wrote:
> Do you have an URL to a description of this bug?
> > The other known issue with svn trunk involves the Highlighter, which doesn't
> > always select the proper excerpt. That wouldn't affect the dev release on
> > CPAN, though.
> This issue would be less problematic if this occurs only sometimes.
It's frequent enough to be unacceptable: 1 in 20, 1 in 30. What happens is
that when the Highlighter trims an excerpt, the keyword that made the excerpt
relevant gets trimmed sometimes, yielding an excerpt that is not obviously
In the grand scheme of things, it's probably not that hard to solve, but I've
been focused elsewhere.
> I think a good release strategy was to get the engine stable first, and
> then release often and early, not waiting for new features too long.
> With this strategy you would get user's feedback more early (and I could
> deploy the engine sooner ;) ).
That would be desirable, but if you include file format and API backwards
compatibility, "get the engine stable" isn't exactly a trivial request. ;)
I've put a ton of effort into modularizing the OO design and the file format
so that supporting back compat will be easier going forward. There will be a
big push sometime soon to write up a draft Apache Lucy File Format
Specification version 0.1, which KS will conform to. If you'd like to
contribute by reviewing that document, I'd appreciate it; the better a job we
do, the sooner we'll "get the engine stable".
More information about the kinosearch