[
https://issues.apache.org/jira/browse/SOLR-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073907#comment-15073907
]
Dennis Gove commented on SOLR-7535:
-----------------------------------
In the Streaming API, read() is called until an EOF tuple is seen. This means
that, even with an UpdateStream, one would have this code
{code}
while(true){
tuple = updateStream.read()
// if # of records is some size, do a commit
if(tuple.EOF){
break
}
}
{code}
I think it's the correct thing for an UpdateStream to swallow the individual
tuples. The use-case you described isn't one I see existing. But if it did then
I could see it being dealt with using a TeeStream. A TeeStream would work
exactly like the unix command tee and take a single input stream and tee it out
into multiple output streams. In this use-case, one would Tee the underlying
searches. But again, I don't see this need actually existing.
> Add UpdateStream to Streaming API and Streaming Expression
> ----------------------------------------------------------
>
> Key: SOLR-7535
> URL: https://issues.apache.org/jira/browse/SOLR-7535
> Project: Solr
> Issue Type: New Feature
> Components: clients - java, SolrJ
> Reporter: Joel Bernstein
> Priority: Minor
> Attachments: SOLR-7535.patch
>
>
> The ticket adds an UpdateStream implementation to the Streaming API and
> streaming expressions. The UpdateStream will wrap a TupleStream and send the
> Tuples it reads to a SolrCloud collection to be indexed.
> This will allow users to pull data from different Solr Cloud collections,
> merge and transform the streams and send the transformed data to another Solr
> Cloud collection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
