[
https://issues.apache.org/jira/browse/LUCENE-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401331#comment-15401331
]
Adrien Grand commented on LUCENE-7317:
--------------------------------------
Auto-prefix terms proved hard to integrate with other APIs (eg. is it right to
require all postings formats to support auto prefixes? is it fine to expose
fake terms to other APIs? (answer to the latter is no as we had to add a couple
checks to make sure we never create terms queries on fake terms)) and at the
same time we got points / bkd trees working, which solved the prefix/range
problem too, and added support for multiple dimensions so it superseded the
auto-prefix efforts.
Even with auto-prefix gone, it is still possible to index prefixes, it just has
to be done up-front by indexing prefixes as the edge n-gram filter would. It is
just a bit less optimized since since we cannot compute some optimal automatic
prefixes based on the data.
> Remove auto prefix terms
> ------------------------
>
> Key: LUCENE-7317
> URL: https://issues.apache.org/jira/browse/LUCENE-7317
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Priority: Minor
> Fix For: master (7.0), 6.2
>
> Attachments: LUCENE-7317.patch
>
>
> This was mostly superseded by the new points API so should we remove
> auto-prefix terms?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
