You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/08/10 17:08:31 UTC

[jira] [Commented] (BEAM-5042) ElasticsearchIO bulk delete

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

Beam JIRA Bot commented on BEAM-5042:
-------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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
>            Priority: P2
>              Labels: stale-P2
>
> 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] contains our current workaround.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)