[
https://issues.apache.org/jira/browse/OAK-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14993218#comment-14993218
]
Chetan Mehrotra commented on OAK-3591:
--------------------------------------
[~tmueller] For contains(., '1234') to work you would also need to set
{{nodeScopeIndex}} to true such that the field value gets indexed as part of
the {{:fulltext}} which used to evaluate fulltext query against nodes i.e. '.'.
Setting just {{analyzed}} enable fulltext query against that specific property
jcr:contains(\@xyz, '1234')
Can you try again by setting {{nodeScopeIndex}}
> Lucene index with 'analyzed=true' sometimes used by mistake
> -----------------------------------------------------------
>
> Key: OAK-3591
> URL: https://issues.apache.org/jira/browse/OAK-3591
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: lucene, query
> Reporter: Thomas Mueller
>
> A Lucene index with a property that is configured as "analyzed = true" is
> sometimes used by mistake. Example:
> {noformat}
> oak:index/testLuceneIndex (oak:QueryIndexDefinition)
> compatVersion: 2
> type: lucene
> async: "async"
> indexRules (nt:unstructured)
> nt:base (nt:unstructured)
> properties (nt:unstructured)
> xyz (nt:unstructured)
> propertyIndex: true,
> analyzed: true,
> name: xyz
> query:
> /jcr:root/content//*[jcr:contains(., '1234')]
> {noformat}
> The index is used, but the result does not contain nodes with properties abc
> = '1234'.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
