Joel: that table is pretty dense -- i would suggest instead using an subsection for each "Stream Function" with a table for the params (name, description, required/optional, sample input) and a code block for a cohesive example of that function.
I would also suggest changing the URL in the "HTTP Interface: Stream Handler" to be a curl command showing the full thing (maybe using POST params for legibility) : Date: Fri, 29 May 2015 12:28:00 +0000 (UTC) : From: "Joel Bernstein (Confluence)" <conflue...@apache.org> : Reply-To: dev@lucene.apache.org : To: comm...@lucene.apache.org : Subject: [CONF] Apache Solr Reference Guide > Streaming Expressions : : [IMAGE] : Joel Bernstein created a page: : : [IMAGE] STREAMING EXPRESSIONS : : Solr 5.2 is the initial release of a new Streaming Expression language. Streaming Expressions, at high level, is a : query language that merges search with parallel computing. : : Streaming Expressions provide a query language that compiles to live Streaming API objects. The Streaming API is a : java API that was introduced in Solr 5.1 that allows developers to harness SolrCloud as a general purpose parallel : computing platform. : : Streaming Expressions provide a higher level query language so you don't have to be a java programmer to access the : parallel computing capabilities in the Streaming API. : : : : : : : : : : : : View Online · Like · Add Comment : Stop watching space · Manage Notifications : This message was sent by Atlassian Confluence 5.0.3, Team Collaboration Software : -Hoss http://www.lucidworks.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
