[
https://issues.apache.org/jira/browse/SOLR-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076396#comment-15076396
]
Joel Bernstein commented on SOLR-7535:
--------------------------------------
for #1, you've got the right plan.
for #2:
The partitionKeys will get added to the search(...). This will partition the
Tuples evenly across the workers. Each worker will then update in parallel.
This syntax should would work:
{code}
parallel(update(search(..., partitionKeys="x")))
{code}
Because each worker gets a partition of the search(...), there should be no
duplication of indexing.
The /update handler simply receives the updates and is unaware of the a
parallelization. The search(...) will continue to use the /export handler.
> 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, 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]
