From 184983280e9b47a24a448b1894b05bd97e221011 Mon Sep 17 00:00:00 2001 From: Mikhail Khludnev Date: Tue, 10 May 2016 21:58:33 +0300 Subject: [PATCH] SOLR-8208: miserable javadoc fixes --- .../transform/SubQueryAugmenterFactory.java | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/solr/core/src/java/org/apache/solr/response/transform/SubQueryAugmenterFactory.java b/solr/core/src/java/org/apache/solr/response/transform/SubQueryAugmenterFactory.java index 829e8cb4fe5..40cc31365e5 100644 --- a/solr/core/src/java/org/apache/solr/response/transform/SubQueryAugmenterFactory.java +++ b/solr/core/src/java/org/apache/solr/response/transform/SubQueryAugmenterFactory.java @@ -48,7 +48,7 @@ import org.apache.solr.search.TermsQParserPlugin; /** * - * This transformer executes subquery per every result document. It must be be given uniq name. + * This transformer executes subquery per every result document. It must be given an unique name. * There might be a few of them, eg fl=*,foo:[subquery],bar:[subquery]. * Every [subquery] occurrence adds a field into a result document with the given name, * the value of this field is a document list, which is a result of executing subquery using @@ -59,19 +59,19 @@ import org.apache.solr.search.TermsQParserPlugin; * are prefixed with the given name and period. eg
* q=*:*&fl=*,foo:[subquery]&foo.q=to be continued&foo.rows=10&foo.sort=id desc * - *

Document field as an input param for subquery

+ *

Document Field As An Input For Subquery Parameters

* - * It's necessary to pass some document field value as a parametr for subquery. It's supported via - * implicit row.fieldname parameter, and can be (but might not only) referred via + * It's necessary to pass some document field value as a parameter for subquery. It's supported via + * implicit row.fieldname parameters, and can be (but might not only) referred via * Local Parameters syntax.
* q=namne:john&fl=name,id,depts:[subquery]&depts.q={!terms f=id v=$row.dept_id}&depts.rows=10 - * Here departmens are retrieved per every employee in search result. We can say that it's like SQL + * Here departments are retrieved per every employee in search result. We can say that it's like SQL * join ON emp.dept_id=dept.id
* Note, when document field has multiple values they are concatenated with comma by default, it can be changed by * foo:[subquery separator=' '] local parameter, this mimics {@link TermsQParserPlugin} to work smoothly with. * - *

Cores and Collections in Cloud

- * use foo:[subquery fromIndex=departments] invoke subquery on another core on this node, it's like + *

Cores And Collections In SolrCloud

+ * use foo:[subquery fromIndex=departments] invoke subquery on another core on the same node, it's like * {@link JoinQParserPlugin} for non SolrCloud mode. But for SolrCloud just (and only) explicitly specify * its' native parameters like collection, shards for subquery, eg
* q=*:*&fl=*,foo:[subquery]&foo.q=cloud&foo.collection=departments