[
https://issues.apache.org/jira/browse/SOLR-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073920#comment-15073920
]
Dennis Gove commented on SOLR-7535:
-----------------------------------
I had an interesting thought related to the call to read().
Should there be some distinction between a ReadStream and a WriteStream. A
ReadStream is one which reads tuples out while a WriteStream is one which
writes tuples in. Up until this point we've only ever had ReadStreams and the
read() method has always made sense. But the UpdateStream is a WriteStream and
maybe it should have a different function, maybe write(). Also, it might be
nice to be able to say in a stream that it's direct incoming stream must be a
WriteStream (for example, a CommitStream would only work on a WriteStream while
a RollupStream would only work on a ReadStream). (though maybe it'd be
interesting to do rollups over the output tuples of an UpdateStream.....).
Thoughts?
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
