[
https://issues.apache.org/jira/browse/OAK-2399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rishabh Maurya updated OAK-2399:
--------------------------------
Attachment: OAK-2399_1.patch
[~tmueller] updated patch with latest trunk version, commit can be found
[here|https://github.com/rishabhmaurya/jackrabbit-oak/commit/1986a5ee5f7d35ae2eb85e9e0efea0ac7b3d3b7d].
{{_exportcontents}} was used to export lucene packages, which is to be used by
custom ScorerProvider.
following points needs to be considered -
1. Exact field names must be known to user implementing customScorer.
2. If query contains orderby clause, then scorer is hardly of any use, so its
better to skip modifying score using custom scorer.
I'll be adding few other points too, which I noted somewhere at time of
implementing.
> Custom scorer for modifying score per documents
> -----------------------------------------------
>
> Key: OAK-2399
> URL: https://issues.apache.org/jira/browse/OAK-2399
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: oak-lucene
> Reporter: Rishabh Maurya
> Assignee: Thomas Mueller
> Fix For: 1.1.8, 1.2
>
> Attachments: OAK-2399_1.patch, OAK-2399_scorer.patch
>
>
> We have search enhancements requests based on search results relevance like -
> 1. boosting score of recently modified documents.
> 2. boosting documents which are created/last updated by current session
> user.(OR boosting on basis specific field value).
> 3. boosting documents with a field value in certain range.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
