[
https://issues.apache.org/jira/browse/SOLR-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073895#comment-15073895
]
Jason Gerlowski commented on SOLR-7535:
---------------------------------------
Thanks for the feedback Joel. (1) and (2) I get. (3)'s a little less clear to
me.
Are you saying that a single {{read()}} on an UpdateStream will call {{read()}}
X times (i.e. batchSize times) on the wrapped stream, package and send those
docs to a collection, and then return a single tuple that says how many tuples
were read?
Is it an issue at all that UpdateStream would be swallowing the individual
tuples? This would prevent users from doing things (other than committing)
with the output of UpdateStream. For example, the use-case below _seems_ valid
to me, but wouldn't be supported with the proposed behavior:
{code}
update(collection5,
merge(
update(collection3, search(collection1, ...)),
update(collection4, search(collection2, ...))
)
)
{code}
Maybe there's not a real need to support that. And Streaming API users would
still be able to do this, they'd just need to do it in 2 steps/requests instead
of 1. I don't have a preference either way; just wanted to bring it up.
> 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]
