jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3591) Lucene index with 'analyzed=true' sometimes used by mistake
Date Mon, 16 Nov 2015 09:53:11 GMT

    [ https://issues.apache.org/jira/browse/OAK-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006423#comment-15006423
] 

Chetan Mehrotra commented on OAK-3591:
--------------------------------------

Merged to 1.0 with 1714529

> 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
>            Assignee: Chetan Mehrotra
>             Fix For: 1.3.11, 1.2.8, 1.0.24
>
>
> 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)

Mime
View raw message