[solr] branch main updated: solr-ref-guide: expand 'eval' streaming expression example; fix a few typos; (#817)

[cp...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

cpoerschke pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/solr.git


The following commit(s) were added to refs/heads/main by this push:
     new de2d9597ddf solr-ref-guide: expand 'eval' streaming expression example; fix a few typos; (#817)
de2d9597ddf is described below

commit de2d9597ddf03041aaf423c9d9cc9e8539d1a036
Author: Christine Poerschke <cp...@apache.org>
AuthorDate: Fri May 27 19:00:50 2022 +0100

    solr-ref-guide: expand 'eval' streaming expression example; fix a few typos; (#817)
---
 .../modules/query-guide/pages/json-facet-api.adoc  |  4 +--
 .../pages/stream-decorator-reference.adoc          | 31 +++++++++++++++++++++-
 .../pages/stream-evaluator-reference.adoc          |  4 ++-
 3 files changed, 35 insertions(+), 4 deletions(-)

diff --git a/solr/solr-ref-guide/modules/query-guide/pages/json-facet-api.adoc b/solr/solr-ref-guide/modules/query-guide/pages/json-facet-api.adoc
index 7ab160fc871..63c3221c20d 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/json-facet-api.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/json-facet-api.adoc
@@ -201,14 +201,14 @@ Number of buckets beyond the `limit` to internally request from shards during a
 
 Larger values can increase the accuracy of the final "Top Terms" returned when the individual shards have very diff top terms.
 
-The default of `-1` causes a hueristic to be applied based on the other options specified.
+The default of `-1` causes a heuristic to be applied based on the other options specified.
 |`refine` |If `true`, turns on distributed facet refining. This uses a second phase to retrieve any buckets needed for the final result from shards that did not include those buckets in their initial internal results, so that every shard contributes to every returned bucket in this facet and any sub-facets.  This makes counts & stats for returned buckets exact.
 |`overrefine` a|
 Number of buckets beyond the `limit` to consider internally during a distributed search when determining which buckets to refine.
 
 Larger values can increase the accuracy of the final "Top Terms" returned when the individual shards have very diff top terms, and the current `sort` option can result in refinement pushing terms lower down the sorted list (ex: `sort:"count asc"`)
 
-The default of `-1` causes a hueristic to be applied based on other options specified.
+The default of `-1` causes a heuristic to be applied based on other options specified.
 |`mincount` |Only return buckets with a count of at least this number. Defaults to `1`.
 |`missing` |A boolean that specifies if a special “missing” bucket should be returned that is defined by documents without a value in the field. Defaults to `false`.
 |`numBuckets` |A boolean. If `true`, adds “numBuckets” to the response, an integer representing the number of buckets for the facet (as opposed to the number of buckets returned). Defaults to `false`.
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/stream-decorator-reference.adoc b/solr/solr-ref-guide/modules/query-guide/pages/stream-decorator-reference.adoc
index 7774a355bac..5f5e590d38a 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/stream-decorator-reference.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/stream-decorator-reference.adoc
@@ -645,7 +645,7 @@ This is similar to the `<<update,update()>>` function described below.
 
 [source,text]
 ----
- delete(collection1
+ delete(collection1,
         batchSize=500,
         search(collection1,
                q=old_data:true,
@@ -690,6 +690,35 @@ In the example above the `eval` expression reads the first tuple from the underl
 It then compiles and
 executes the string streaming expression in the `expr_s` field.
 
+Example:
+
+[source,text]
+----
+eval(select(
+  echo("tuple(answer=42)"),
+  echo as expr_s
+))
+----
+
+Output:
+
+[source,json]
+----
+{
+  "result-set": {
+    "docs": [
+      {
+        "answer": "42"
+      },
+      {
+        "EOF": true,
+        "RESPONSE_TIME": 0
+      }
+    ]
+  }
+}
+----
+
 == executor
 
 The `executor` function wraps a stream source that contains streaming expressions, and executes the expressions in parallel.
diff --git a/solr/solr-ref-guide/modules/query-guide/pages/stream-evaluator-reference.adoc b/solr/solr-ref-guide/modules/query-guide/pages/stream-evaluator-reference.adoc
index c6bb3f9a4a6..ff4ef07db7b 100644
--- a/solr/solr-ref-guide/modules/query-guide/pages/stream-evaluator-reference.adoc
+++ b/solr/solr-ref-guide/modules/query-guide/pages/stream-evaluator-reference.adoc
@@ -1238,7 +1238,9 @@ The `length` function returns the length of a numeric array.
 [source,text]
 length(numericArray)
 
-== lerp (TOD0)
+== lerp
+
+// TODO
 
 == loess