[
https://issues.apache.org/jira/browse/OAK-4516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430875#comment-15430875
]
Vikas Saurabh edited comment on OAK-4516 at 8/22/16 5:12 PM:
-------------------------------------------------------------
Backport [r1751376|https://svn.apache.org/r1751376] to 1.2 in
[r1757184|https://svn.apache.org/r1757184]. Not backporting to 1.0 as it
requires OAK-2177 too.
was (Author: catholicon):
Backport [r1751376|https://svn.apache.org/r1751376] to 1.2 in
[r1757184|https://svn.apache.org/r1757184].
> Configurable option to lucene index defs to index original (unanalyzed value
> as well)
> -------------------------------------------------------------------------------------
>
> Key: OAK-4516
> URL: https://issues.apache.org/jira/browse/OAK-4516
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: lucene
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
> Fix For: 1.6, 1.5.5, 1.4.7, 1.2.19
>
> Attachments: OAK-4516.patch
>
>
> It's sometimes useful to have original value being indexed to be stored as a
> term. One use-case could be like:
> * consider a couple of values to be indexed as {{abc_def}}, {{abcdef}}
> * On query, it seems reasonable to get both values for a query for {{abc*}}
> * On query, at times, it might be useful to expect {{abc_def}} for
> {{abc_d\*}} or {{abc_\*}}
> Currently, the values would get indexed like:
> * {{abc_def}} -> {{\[abc], \[def]}}
> * {{abcdef}} -> {{\[abcdef]}}
> So, the query {{abc*}} would only fetch {{abcdef}}, while {{abc_d\*}} or
> {{abc_\*}} won't fetch anything.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
