lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From m...@apache.org
Subject lucene-solr:branch_6x: SOLR-8208: miserable javadoc fixes
Date Tue, 10 May 2016 18:58:58 GMT
Repository: lucene-solr
Updated Branches:
  refs/heads/branch_6x 03a06bb3a -> 184983280


SOLR-8208: miserable javadoc fixes


Project: http://git-wip-us.apache.org/repos/asf/lucene-solr/repo
Commit: http://git-wip-us.apache.org/repos/asf/lucene-solr/commit/18498328
Tree: http://git-wip-us.apache.org/repos/asf/lucene-solr/tree/18498328
Diff: http://git-wip-us.apache.org/repos/asf/lucene-solr/diff/18498328

Branch: refs/heads/branch_6x
Commit: 184983280e9b47a24a448b1894b05bd97e221011
Parents: 03a06bb
Author: Mikhail Khludnev <mkhl@apache.org>
Authored: Tue May 10 21:58:33 2016 +0300
Committer: Mikhail Khludnev <mkhl@apache.org>
Committed: Tue May 10 21:58:33 2016 +0300

----------------------------------------------------------------------
 .../response/transform/SubQueryAugmenterFactory.java  | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/lucene-solr/blob/18498328/solr/core/src/java/org/apache/solr/response/transform/SubQueryAugmenterFactory.java
----------------------------------------------------------------------
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 829e8cb..40cc313 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 <code>fl=*,foo:[subquery],bar:[subquery]</code>.

  * 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 <br>
  * <code>q=*:*&amp;fl=*,foo:[subquery]&amp;foo.q=to be continued&amp;foo.rows=10&amp;foo.sort=id
desc</code>
  * 
- * <h3>Document field as an input param for subquery</h3>
+ * <h3>Document Field As An Input For Subquery Parameters</h3>
  * 
- * It's necessary to pass some document field value as a parametr for subquery. It's supported
via 
- * implicit <code>row.<i>fieldname</i></code> 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 <code>row.<i>fieldname</i></code> parameters, and can
be (but might not only) referred via
  *  Local Parameters syntax.<br>
  * <code>q=namne:john&amp;fl=name,id,depts:[subquery]&amp;depts.q={!terms f=id
v=$row.dept_id}&amp;depts.rows=10</code>
- * 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
  * <code> join ON emp.dept_id=dept.id </code><br>
  * Note, when document field has multiple values they are concatenated with comma by default,
it can be changed by
  * <code>foo:[subquery separator=' ']</code> local parameter, this mimics {@link
TermsQParserPlugin} to work smoothly with.
  * 
- * <h3>Cores and Collections in Cloud</h3>
- * use <code>foo:[subquery fromIndex=departments]</code> invoke subquery on another
core on this node, it's like
+ * <h3>Cores And Collections In SolrCloud</h3>
+ * use <code>foo:[subquery fromIndex=departments]</code> invoke subquery on another
core on the same node, it's like
  *  {@link JoinQParserPlugin} for non SolrCloud mode. <b>But for SolrCloud</b>
just (and only) <b>explicitly specify</b> 
  * its' native parameters like <code>collection, shards</code> for subquery,
eg<br>
  *  <code>q=*:*&amp;fl=*,foo:[subquery]&amp;foo.q=cloud&amp;foo.collection=departments</code>


Mime
View raw message