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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2016/11/25 02:24:59 UTC

[jira] [Commented] (OAK-3960) Boosted field don't work if parent nodes are covered in aggregate definition

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

Vikas Saurabh commented on OAK-3960:
------------------------------------

[~chetanm], can you please see if the use-case in description is indeed expected? Similar (rather a bit more elaborate) case is covered in the test in the [patch|^OAK-3960.patch] too.

> Boosted field don't work if parent nodes are covered in aggregate definition
> ----------------------------------------------------------------------------
>
>                 Key: OAK-3960
>                 URL: https://issues.apache.org/jira/browse/OAK-3960
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Vikas Saurabh
>            Assignee: Vikas Saurabh
>              Labels: lucene
>             Fix For: 1.6
>
>         Attachments: OAK-3960.patch
>
>
> With index def of the form:
> {noformat}
> +/indexName/indexRules/nodeType1/properties/prop0
>      -name=subChild/indexedProp
>      -nodeScopeIndex=true
>      -boost=2.0
> +indexName/aggregates/nodeType1/include0
>      -path=subChild
>      -relativeNode=true
> {noformat}
> A query like {{//element(*, nodeType1)\[jcr:contains(subChild, 'bar')]}} should rank nodes with {{subChild/\@indexedProp=bar}} above other nodes with any prop {{=bar}} under subChild.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)