rseitz commented on code in PR #1154:
URL: https://github.com/apache/solr/pull/1154#discussion_r1015524337
##########
solr/solrj/src/java/org/apache/solr/common/params/QueryElevationParams.java:
##########
@@ -59,4 +59,11 @@ public interface QueryElevationParams {
* set this to true. False by default.
*/
String ELEVATE_ONLY_DOCS_MATCHING_QUERY = "elevateOnlyDocsMatchingQuery";
+
+ /**
+ * By default, the component respects the fq parameter. If you want to
elevate documents that do
+ * not match the provided filters, tag the filters in question via the local
parameter syntax
+ * fq={!tag=t1}field1:value1 and then specify the tags for exclusion via
elevate.excludeTag=t1
Review Comment:
Looking at the other parameter names, I see that some include a form of
"elevate" (`enableElevation`, `forceElevation`, `useConfiguredElevatedOrder`,
`elevateIds`) and others don't (`exclusive`, `markExcludes`, `excludeIds`).
None of them include dot. Is it better to use a prefix naming standard for all
new params, starting now, or try to be consistent with what's already there?
I'm not seeing much of a pattern in the existing param names to try to match,
so I'll plan to leave this as `elevate.excludeTags` unless others have feedback?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
