[ 
https://issues.apache.org/jira/browse/SOLR-8487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15440446#comment-15440446
 ] 

Joel Bernstein commented on SOLR-8487:
--------------------------------------

The original patch had the update function do it's own commits. But it was 
taken out because if an expression is doing parallel updates there would be 
multiple workers committing at the same time. So the commit function is needed 
to support this scenario:

{code}
commit(parallel(update(search())))
{code}

So I think we're left with the choice of using the data in the tuples returned 
by the update stream, or leaving it decoupled.



> Add CommitStream to Streaming API and Streaming Expressions
> -----------------------------------------------------------
>
>                 Key: SOLR-8487
>                 URL: https://issues.apache.org/jira/browse/SOLR-8487
>             Project: Solr
>          Issue Type: New Feature
>    Affects Versions: 6.0
>            Reporter: Jason Gerlowski
>            Priority: Minor
>             Fix For: 6.0
>
>         Attachments: SOLR-8487.patch
>
>
> (Paraphrased from Joel's idea/suggestions in the comments of SOLR-7535).
> With SOLR-7535, users can now index documents/tuples using an UpdateStream.  
> However, there's no way currently using the Streaming API to force a commit 
> on the collection that received these updates.
> The purpose of this ticket is to add a CommitStream, which can be used to 
> trigger commit(s) on a given collection.
> The proposed usage/behavior would look a little bit like:
> {{commit(collection, parallel(update(search()))}}
> Note that...
> 1.) CommitStream has a positional collection parameter, to indicate which 
> collection to commit on. (Alternatively, it could recurse through 
> {{children()}} nodes until it finds the UpdateStream, and then retrieve the 
> collection from the UpdateStream).
> 2.) CommitStream forwards all tuples received by an underlying, wrapped 
> stream.
> 3.) CommitStream commits when the underlying stream emits its EOF tuple. 
> (Alternatively, it could commit every X tuples, based on a parameter).



--
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

Reply via email to