[lucene-solr] 01/02: SOLR-13105: Add copy to search-sample page

[jb...@apache.org]

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

jbernste pushed a commit to branch SOLR-13105-visual
in repository https://gitbox.apache.org/repos/asf/lucene-solr.git

commit f33485e0b06927a0b807f6596d9411410c194bdc
Author: Joel Bernstein <jb...@apache.org>
AuthorDate: Tue Jun 18 07:02:01 2019 -0400

    SOLR-13105: Add copy to search-sample page
---
 solr/solr-ref-guide/src/search-sample.adoc | 60 ++++++++----------------------
 1 file changed, 16 insertions(+), 44 deletions(-)

diff --git a/solr/solr-ref-guide/src/search-sample.adoc b/solr/solr-ref-guide/src/search-sample.adoc
index 6695b14..aeb146f 100644
--- a/solr/solr-ref-guide/src/search-sample.adoc
+++ b/solr/solr-ref-guide/src/search-sample.adoc
@@ -16,14 +16,11 @@
 // specific language governing permissions and limitations
 // under the License.
 
-This section of the user guide explores techniques
-for retrieving streams of data from Solr and vectorizing the
-numeric fields.
 
-See the section <<term-vectors.adoc#term-vectors,Text Analysis and Term Vectors>> which describes how to
-vectorize text fields.
 
-== Searching and Sorting
+== Searching
+
+=== Exploring
 
 The *search* function can be used to search a Solr Cloud collection and return a
 result set.
@@ -32,12 +29,6 @@ Below is an example of the most basic *search* function called from the Zeppelin
 Zeppelin-Solr sends the *seach(testapp)* call to the /stream handler and displays the results
 in *table* format.
 
-This simple example is instructive for how Zeppelin-Solr handles all Streaming Expressions,
-which by definition return a stream of tuples or name/value pair documents. Zeppelin-Solr creates a
-table from the result set with one row per tuple. Each column of the table represents a field in the tuples.
-
-Once the tuples have been loaded into a table the columns in the table can be visualized by switching
-to the various visualizations and configuring the settings.
 
 In the example the search function passed only the name of the collection being search. This returns
 a result set of 10 records showing all fields in and unspecified order. This simple function is useful
@@ -45,6 +36,8 @@ for exploring the fields in the data and understanding how to start refining the
 
 image::images/math-expressions/search1.png[]
 
+==== Searching and Sorting
+
 Once we see the format of the records we can add parameters to the *search* function to begin analyzing
 the data.
 
@@ -70,37 +63,16 @@ select from the a very specific slice of the index. In this example it's the
 
 == Sampling
 
-[source,text]
-----
-random(testapp)
-----
-
-When this expression is sent to the `/stream` handler it responds with:
-
-[source,json]
-----
-{
-  "result-set": {
-    "docs": [
-      {
-        "response_d": 1080.3692514541938,
-        "new_response": 10803.692514541937
-      },
-      {
-        "response_d": 1067.441598608506,
-        "new_response": 10674.41598608506
-      },
-      {
-        "response_d": 1059.8400090891566,
-        "new_response": 10598.400090891566
-      },
-      {
-        "EOF": true,
-        "RESPONSE_TIME": 12
-      }
-    ]
-  }
-}
-----
+=== Univariate Scatter Plots
+
+=== Bivariate Scatter Plots
+
+
+
 == Aggregations
 
+=== facet
+
+=== facet2D
+
+=== timeseries
\ No newline at end of file