[
https://issues.apache.org/jira/browse/SOLR-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064009#comment-15064009
]
Jason Gerlowski commented on SOLR-7525:
---------------------------------------
bq. the tuples in B aren't used for anything and are dropped as soon as
possible. The reason they make use of the ReducerStream is because B having 1
instance of some tuple found in A is the same as B having 100 instances of some
tuple found in A. Whether its 1 or 100 the tuple exists in B so its twin in A
can either be returned from A or not. For this reason the size of the
ReducerStream can always just be 1
Ah, this makes sense now. I was misreading {{ReducerStream}}. That makes most
of the rest of my comment invalid. But, learn something new every day I
guess...Looking forward to seeing your update to the patch, so I can get a
better idea of how this should work. Thanks for the clarification Dennis.
> Add ComplementStream to the Streaming API and Streaming Expressions
> -------------------------------------------------------------------
>
> Key: SOLR-7525
> URL: https://issues.apache.org/jira/browse/SOLR-7525
> Project: Solr
> Issue Type: New Feature
> Components: SolrJ
> Reporter: Joel Bernstein
> Priority: Minor
> Attachments: SOLR-7525.patch
>
>
> This ticket adds a ComplementStream to the Streaming API and Streaming
> Expression language.
> The ComplementStream will wrap two TupleStreams (StreamA, StreamB) and emit
> Tuples from StreamA that are not in StreamB.
> Streaming API Syntax:
> {code}
> ComplementStream cstream = new ComplementStream(streamA, streamB, comp);
> {code}
> Streaming Expression syntax:
> {code}
> complement(search(...), search(...), on(...))
> {code}
> Internal implementation will rely on the ReducerStream. The ComplementStream
> can be parallelized using the ParallelStream.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
