[
https://issues.apache.org/jira/browse/SOLR-16496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627788#comment-17627788
]
Rudi Seitz commented on SOLR-16496:
-----------------------------------
Thanks, [~dsmiley], I've updated the PR based on your feedback. Added support
for tagging individual filters using LocalParams syntax and then specifying the
tags to exclude via {{elevate.excludeTags}}
Does the updated PR match what you had in mind?
A specific question came up: To create the set of filters to exclude based on
their tags, I [adapted some
code|https://github.com/apache/solr/pull/1154/commits/2a97643ce758029e5d68978eb0633fced927b515#diff-26b681890de6a262a6c94485956aa1ada9d2bff306dabe79962ec459843f76faR599]
from
[FacetProcessor#handleFilterExclusions()|https://github.com/apache/solr/blob/26195c82493422cb9d6d4bdf9d4452046e7b3f67/solr/core/src/java/org/apache/solr/search/facet/FacetProcessor.java#L192]
I thought about abstracting it into a common utility method but wanted to
avoid touching FacetProcessor for now. What would you recommend re: next steps?
> provide option for Query Elevation Component to bypass filters
> --------------------------------------------------------------
>
> Key: SOLR-16496
> URL: https://issues.apache.org/jira/browse/SOLR-16496
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SearchComponents - other
> Reporter: Rudi Seitz
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Query Elevation Component respects the fq parameter.
> A document listed in elevate.xml or specified via the {{elevateIds}}
> parameter must match the provided filter queries in order to be included in
> the result set for a given query. Documents that don't match the filter
> queries will be excluded regardless of whether they are supposed to be
> "elevated."
> In some cases, this behavior is desirable; in other cases, it is not. For
> example, an ecommerce landing page might filter products according to whether
> they are in stock ({{{}fq=inStock:true{}}}) but might wish to show certain
> promoted products regardless of inventory.
> This ticket asks for an {{elevateFilteredDocs}} parameter that could be set
> to true to include elevated documents in the result set regardless of whether
> they match the provided filter queries. The default would be false, in
> accordance with the current behavior.
> This parameter would allow elevated documents to "bypass" the provided
> filters, while keeping the filters in place for non-elevated documents.
> From an implementation standpoint, this parameter could be supported with
> code in {{QueryElevationComponent#setQuery}} that updates the filter queries
> in similar way to how the main query is updated. When
> {{{}elevateFilteredDocs=true{}}}, each filter query would become a boolean
> "OR" of the original filter query with a second query matching the elevated
> documents by id.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
