lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] [Commented] (LUCENE-4285) Improve FST API usability for mere mortals
Date Sat, 06 Oct 2012 18:55:02 GMT


Dawid Weiss commented on LUCENE-4285:

Things are more difficult than they seem at the surface. An elegant solution would encode
an empty automaton without any extra flags or checks. In an arc based representation there
is simply no notion of an "empty" set of arcs though -- there needs to be at least one and
if it's present on the root state then, well, it's no longer an empty automaton. Like I said
-- this can be modeled with an initial state transition (the symbol doesn't matter); if this
transition is final then this the automaton is empty (there is no actual root state). But
this also changes how traversals are implemented and would affect all of the existing code.
> Improve FST API usability for mere mortals
> ------------------------------------------
>                 Key: LUCENE-4285
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/FSTs
>            Reporter: David Smiley
> FST technology is something that has brought amazing advances to Lucene, yet the API
is hard to use for the vast majority of users like me.  I know that performance of FSTs is
really important, but surely a lot can be done without sacrificing that.
> (comments will hold specific ideas and problems)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message