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

Wout Scheepers updated BEAM-5042:
---------------------------------
    Description: 
Since Beam 2.5.0 partial updates are supported, the only thing I’m missing is 
the ability to send bulk *delete* requests.

 
As ES 6.x support is being added which going to be different on the write() 
path (https://issues.apache.org/jira/browse/BEAM-3199) , I decided to postpone 
the creation of a pull request that supports this until the ES6 feature is 
released.
 
[https://gist.github.com/wscheep/26cca4bda0145ffd38faf7efaf2c21b9|https://gist.github.com/wscheep/26cca4bda0145ffd38faf7efaf2c21b9]]
 contains our current workaround.

  was:
Since Beam 2.5.0 partial updates are supported, the only thing I’m missing is 
the ability to send bulk *delete* requests.[

|https://gist.github.com/wscheep/26cca4bda0145ffd38faf7efaf2c21b9]

As ES 6.x support is being added which going to be different on the write() 
path (https://issues.apache.org/jira/browse/BEAM-3199) , I decided to postpone 
the creation of a pull request that supports this until the ES6 feature is 
released.


> ElasticsearchIO bulk delete
> ---------------------------
>
>                 Key: BEAM-5042
>                 URL: https://issues.apache.org/jira/browse/BEAM-5042
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-elasticsearch
>            Reporter: Wout Scheepers
>            Assignee: Etienne Chauchot
>            Priority: Major
>
> Since Beam 2.5.0 partial updates are supported, the only thing I’m missing is 
> the ability to send bulk *delete* requests.
>  
> As ES 6.x support is being added which going to be different on the write() 
> path (https://issues.apache.org/jira/browse/BEAM-3199) , I decided to 
> postpone the creation of a pull request that supports this until the ES6 
> feature is released.
>  
> [https://gist.github.com/wscheep/26cca4bda0145ffd38faf7efaf2c21b9|https://gist.github.com/wscheep/26cca4bda0145ffd38faf7efaf2c21b9]]
>  contains our current workaround.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to