dsmiley commented on a change in pull request #780: SOLR-11866: Support
efficient subset matching in query elevation rules
URL: https://github.com/apache/lucene-solr/pull/780#discussion_r303893047
##########
File path: solr/solr-ref-guide/src/the-query-elevation-component.adoc
##########
@@ -93,11 +93,19 @@ Elevated query results can be configured in an external
XML file specified in th
<doc id="MA147LL/A" /> <!-- put the actual ipod at the top -->
<doc id="IW-02" exclude="true" /> <!-- exclude this cable -->
</query>
+
+ <query text="foo bill" match="subset">
+ <doc id="11" />
+ </query>
</elevate>
----
In this example, the query "foo bar" would first return documents 1, 2 and 3,
then whatever normally appears for the same query. For the query "ipod", it
would first return "MA147LL/A", and would make sure that "IW-02" is not in the
result set.
+Notice the `match` parameter with the value "subset" for the third rule. A
query "bill bar foo" would trigger this rule because the rule defines a subset
of terms to appear in the query, in any order. This query would elevate
document 11 on top.
+The `match` parameter accepts either "exact" (by default) or "subset" values.
+Subset matching is scalable, one can add many rules with the match="subset"
parameter.
Review comment:
the match="subset" needs code style.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
