lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dawid Weiss (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3017) FST should differentiate between final vs non-final stop nodes
Date Mon, 11 Apr 2011 11:09:05 GMT


Dawid Weiss commented on LUCENE-3017:

Ehm... an automaton with zero-arc nodes that are not final is no no longer an automaton, but
a graph of some sort... I mean -- what is the interpretation of an empty non-final node? "There
is no sequence in the input that corresponds to this path and it is a prefix of some path
in the input that you can't get from this automaton", right? 

This slowly becomes very confusing... the patch looks all right, but I'm thinking if the API
overall is still clear.

> FST should differentiate between final vs non-final stop nodes
> --------------------------------------------------------------
>                 Key: LUCENE-3017
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Michael McCandless
>            Priority: Minor
>             Fix For: 4.0
>         Attachments: LUCENE-3017.patch
> I'm breaking out this one improvement from LUCENE-2948...
> Currently, if a node has no outgoing edges (a "stop node") the FST
> forcefully marks this as a final node, but it need not do this.  Ie,
> whether that node is final or not should be orthogonal to whether it
> has arcs leaving or not.

This message is automatically generated by JIRA.
For more information on JIRA, see:

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

View raw message