[ 
https://issues.apache.org/jira/browse/SOLR-10292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929818#comment-15929818
 ] 

Joel Bernstein commented on SOLR-10292:
---------------------------------------

I was basing the name off of this:
http://docs.aws.amazon.com/machine-learning/latest/dg/data-transformations-reference.html#cartesian-product-transformation

One of the things I was considering is making the cartesian function be the 
opposite of *reduce*. In this scenario we allow for cartesian operations that 
would take in a single tuple and return an array of tuples. The tuples would 
then be streamed from the cartesian function rather then returning the array.

This would allow us to add cartesian operations on text fields which would use 
tokenizers to emit sentences, shingles, key phrases etc.. 

> Add cartesian Streaming Expression to build cartesian products from 
> multi-value fields
> --------------------------------------------------------------------------------------
>
>                 Key: SOLR-10292
>                 URL: https://issues.apache.org/jira/browse/SOLR-10292
>             Project: Solr
>          Issue Type: New Feature
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Joel Bernstein
>
> Currently all the Streaming Expression such as rollups, intersections, fetch 
> etc, work on single value fields. The *cartesian* expression would create a 
> stream of tuples from a single tuple with a multi-value field. This would 
> allow multi-valued fields to be operated on by the wider library of Streaming 
> Expression.
> For example a single tuple with a multi-valued field:
> id: 1
> author: [Jim, Jack, Steve]
> Would be transformed in the following three tuples:
> id:1
> author:Jim
> id:1
> author:Jack
> id:1
> author:Steve



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to