[
https://issues.apache.org/jira/browse/LUCENE-3121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189137#comment-13189137
]
David Smiley commented on LUCENE-3121:
--------------------------------------
bq. That would be interesting! Or, maybe to DocValues instead...
Yes, that is in fact the very idea I had originally that I raised on the list
that you in turn created this JIRA issue for. It was almost a year ago so
perhaps you forgot. Well this JIRA issue would be the first step, the next
step would be another JIRA issue for Field Cache integration and another for
DocValues. I feel a tad guilty for suggesting this work without taking part...
I'm neck deep in geospatial Lucene extensions.
> FST should offer lookup-by-output API when output strictly increases
> --------------------------------------------------------------------
>
> Key: LUCENE-3121
> URL: https://issues.apache.org/jira/browse/LUCENE-3121
> Project: Lucene - Java
> Issue Type: Improvement
> Components: core/other
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 3.6, 4.0
>
> Attachments: LUCENE-3121.patch
>
>
> Spinoff from "FST and FieldCache" java-dev thread
> http://lucene.markmail.org/thread/swoawlv3fq4dntvl
> FST is able to associate arbitrary outputs with the sorted input keys, but in
> the special (and, common) case where the function is strictly monotonic (each
> output only "increases" vs prior outputs), such as mapping to term ords or
> mapping to file offsets in the terms dict, we should offer a lookup-by-output
> API that efficiently walks the FST and locates input key (exact or floor or
> ceil) matching that output.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
