lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Gove (JIRA)" <>
Subject [jira] [Updated] (SOLR-8487) Add CommitStream to Streaming API and Streaming Expressions
Date Thu, 25 Aug 2016 14:25:20 GMT


Dennis Gove updated SOLR-8487:
    Attachment: SOLR-8487.patch

No tests (will add soon).
Doesn't add any summary tuples - not sure if these are necessary.

Supports setting batchSize, waitFlush, waitSearcher, and softCommit settings.

> Add CommitStream to Streaming API and Streaming Expressions
> -----------------------------------------------------------
>                 Key: SOLR-8487
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message