mirror of https://github.com/apache/lucene.git
Ref Guide: Remove place holders
This commit is contained in:
parent
a1692c160a
commit
1921b61ba8
|
@ -20,10 +20,6 @@
|
|||
// specific language governing permissions and limitations
|
||||
// under the License.
|
||||
|
||||
== cartesianProduct
|
||||
//TODO
|
||||
|
||||
|
||||
== classify
|
||||
|
||||
The `classify` function classifies tuples using a logistic regression text classification model. It was designed specifically to work with models trained using the <<stream-sources.adoc#train,train function>>. The `classify` function uses the <<stream-sources.adoc#model,model function>> to retrieve a stored model and then scores a stream of tuples using the model. The tuples read by the classifier must contain a text field that can be used for classification. The classify function uses a Lucene analyzer to extract the features from the text so the model can be applied. By default the `classify` function looks for the analyzer using the name of text field in the tuple. If the Solr schema on the worker node does not contain this field, the analyzer can be looked up in another field by specifying the `analyzerField` parameter.
|
||||
|
@ -534,9 +530,6 @@ merge(
|
|||
on="fieldA asc")
|
||||
----
|
||||
|
||||
== list
|
||||
// TODO
|
||||
|
||||
== null
|
||||
|
||||
The null expression is a useful utility function for understanding bottlenecks when performing parallel relational algebra (joins, intersections, rollups etc.). The null function reads all the tuples from an underlying stream and returns a single tuple with the count and processing time. Because the null stream adds minimal overhead of it's own, it can be used to isolate the performance of Solr's /export handler. If the /export handlers performance is not the bottleneck, then the bottleneck is likely occurring in the workers where the stream decorators are running.
|
||||
|
|
|
@ -412,30 +412,6 @@ or(and(fieldA,fieldB),fieldC) // (fieldA && fieldB) || fieldC
|
|||
or(fieldA,fieldB,fieldC,and(fieldD,fieldE),fieldF)
|
||||
----
|
||||
|
||||
== analyze
|
||||
//TODO
|
||||
|
||||
== second
|
||||
//TODO
|
||||
|
||||
== minute
|
||||
//TODO
|
||||
|
||||
== hour
|
||||
//TODO
|
||||
|
||||
== day
|
||||
//TODO
|
||||
|
||||
== month
|
||||
//TODO
|
||||
|
||||
== year
|
||||
//TODO
|
||||
|
||||
== convert
|
||||
//TODO
|
||||
|
||||
== raw
|
||||
|
||||
The `raw` function will return whatever raw value is the parameter. This is useful for cases where you want to use a string as part of another evaluator.
|
||||
|
@ -457,5 +433,3 @@ raw(true) // "true" (note: this returns the string "true" and not the boolean tr
|
|||
eq(raw(fieldA), fieldA) // true if the value of fieldA equals the string "fieldA"
|
||||
----
|
||||
|
||||
== UUID
|
||||
//TODO
|
||||
|
|
Loading…
Reference in New Issue