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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/09/08 11:25:46 UTC

[jira] [Commented] (OAK-3367) Boosting fields not working as expected

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

Chetan Mehrotra commented on OAK-3367:
--------------------------------------

Added ignored test to illustrate the issue in http://svn.apache.org/r1701750. Also updated the docs to mention that feature is not working

> Boosting fields not working as expected
> ---------------------------------------
>
>                 Key: OAK-3367
>                 URL: https://issues.apache.org/jira/browse/OAK-3367
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>             Fix For: 1.3.6
>
>
> When the boost support was added the intention was to support a usecase like 
> {quote}
> For the fulltext search on a node where the fulltext content is derived from multiple field it should be possible to boost specific text contributed by individual field. Meaning that if a title field is boosted more than description, the title (part) in the fulltext field will mean more than the description (part) in the fulltext field.
> {quote}
> This would enable a user to perform a search like _/jcr:root/content/geometrixx-outdoors/en//element(*, cq:Page)\[jcr:contains(., 'Keyword')\]_ and get a result where pages having 'Keyword' in title come above in search result compared to those where Keyword is found in description.
> Current implementation just sets the boost while add the field value to fulltext field with the intention that Lucene would use the boost as explained above. However it does not work like that and boost value gets multiplies with other field and hence boosting does not work as expected



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