[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507037#comment-16507037
]
ASF subversion and git services commented on SOLR-11865:
--------------------------------------------------------
Commit a06256ccee8742eaf47ac1f2c12ec8e68a70a163 in lucene-solr's branch
refs/heads/master from broustant
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=a06256c ]
SOLR-11865: QueryElevationComponent changes
* new useConfiguredElevatedOrder setting
* more extensible (customizable via subclass)
** ElevationProvider
** handleInitializationException with cause enum
* use BytesRef for uniqueKey ID pervasively instead of String.
* ElevatorComparatorSource now reuses getBoostedDocs logic
* setSort will short-circuit if there are no elevated Ids
* extensive refactoring and affects some interrelated components
> Refactor QueryElevationComponent to prepare query subset matching
> -----------------------------------------------------------------
>
> Key: SOLR-11865
> URL: https://issues.apache.org/jira/browse/SOLR-11865
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SearchComponents - other
> Affects Versions: master (8.0)
> Reporter: Bruno Roustant
> Priority: Minor
> Labels: QueryComponent
> Fix For: master (8.0)
>
> Attachments:
> 0001-Refactor-QueryElevationComponent-to-introduce-Elevat.patch,
> 0002-Refactor-QueryElevationComponent-after-review.patch,
> 0003-Remove-exception-handlers-and-refactor-getBoostDocs.patch,
> SOLR-11865.patch, SOLR-11865.patch, SOLR-11865.patch, SOLR-11865.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The goal is to prepare a second improvement to support query terms subset
> matching or query elevation rules.
> Before that, we need to refactor the QueryElevationComponent. We make it
> extendible. We introduce the ElevationProvider interface which will be
> implemented later in a second patch to support subset matching. The current
> full-query match policy becomes a default simple MapElevationProvider.
> - Add overridable methods to handle exceptions during the component
> initialization.
> - Add overridable methods to provide the default values for config properties.
> - No functional change beyond refactoring.
> - Adapt unit test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
