[
https://issues.apache.org/jira/browse/SOLR-11865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420272#comment-16420272
]
Bruno Roustant commented on SOLR-11865:
---------------------------------------
1- InitializationExceptionHandler & LoadingExceptionHandler:
At Salesforce (i.e. in a multi-tenant context) we allow each organization admin
to update the list of elevation rules dynamically. When some rules are updated,
the core corresponding to the organization is updated to reload the elevation
rules XML. It is important to note that the organization admin - the person who
defines the elevation rules - is not a Solr admin expert. He needs to get clear
feedback on any error that may prevent the rules to be loaded. The XML rules
are more considered as dynamic config rather than static config.
In its original version, the QueryElevationComponent simply throws an exception.
In this new version, it differentiates the error cause and lets an extending
class (e.g. specific Salesforce extension) override the loading exception and
take appropriate actions (logging, warning, etc) instead of simply throwing the
Solr exception.
> 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,
> SOLR-11865.patch
>
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
