[
https://issues.apache.org/jira/browse/LUCENE-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018401#comment-13018401
]
Michael McCandless commented on LUCENE-3017:
--------------------------------------------
Well... for LUCENE-2948, I need this to handle term prefixes that are
in the terms index and are also valid terms.
For example, I could have term "foo", a prefix of many other terms
("foobar", "foobaz", etc), and so the path f-o-o is in the terms index
(pointing to a block that has all these other terms), ie ending on a
zero-arc node.
If that ending zero-arc node is final, I know "foo" is a valid term
and I must seek to the block to load it, but if it's not final, I know
it cannot exist in the index, and I can fail-fast (return NOT_FOUND
from seek("foo")).
> FST should differentiate between final vs non-final stop nodes
> --------------------------------------------------------------
>
> Key: LUCENE-3017
> URL: https://issues.apache.org/jira/browse/LUCENE-3017
> 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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
