You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2015/12/02 17:26:11 UTC
[jira] [Resolved] (OAK-3594) Consider using LuceneDictionary in
suggester
[ https://issues.apache.org/jira/browse/OAK-3594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tommaso Teofili resolved OAK-3594.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.4)
1.3.11
implemented in OAK-3149
> Consider using LuceneDictionary in suggester
> --------------------------------------------
>
> Key: OAK-3594
> URL: https://issues.apache.org/jira/browse/OAK-3594
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: 1.3.11
>
>
> Currently Lucene suggester is based on {{DocumentDictionary}} which builds suggestions upon stored values of a certain field (in this case _:suggest_), however it may be better to stick to plain indexed terms via a {{LuceneDictionary}} as this would allow to save some space in the index (:suggest field wouldn't have to be stored) and we can leverage per index (configurable) analyzer in order to tweak how suggestions will be returned: using a _KeywordAnalyzer_ would result in same behaviour we currently have, using a tokenizing Analyzer will result in term level suggestions (tokens instead of field values).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)