[jira] [Updated] (USERGRID-655) More than one connection does not get created when running batch index on connection edges

["Jeffrey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/USERGRID-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeffrey  updated USERGRID-655:
------------------------------
    Sprint: Usergrid 19  (was: Usergrid 18)

> More than one connection does not get created when running batch index on connection edges
> ------------------------------------------------------------------------------------------
>
>                 Key: USERGRID-655
>                 URL: https://issues.apache.org/jira/browse/USERGRID-655
>             Project: Usergrid
>          Issue Type: Story
>          Components: Stack
>            Reporter: George Reyes
>            Assignee: George Reyes
>
> When running the following code in indexEntity         final Observable<IndexOperationMessage>  batches =  observable.buffer( indexFig.getIndexBatchSize() )
>             //map into batches based on our buffer size
>             .flatMap( buffer -> Observable.from( buffer )
>                 //collect results into a single batch
>                 .collect( () -> ei.createBatch(), ( batch, indexEdge ) -> {
>                     logger.debug( "adding edge {} to batch for entity {}", indexEdge, entity );
>                     batch.index( indexEdge, entity );
>                 } )
>                     //return the future from the batch execution
>                 .flatMap( batch -> batch.execute() ) );
> When run with more than one SearchEdge only one SearchEdge is indexed into elasticsearch. Despite both search edges having the same document id. The batch executes but only one connection gets indexed in elasticsearch. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)