[
https://issues.apache.org/jira/browse/NIFI-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124703#comment-16124703
]
ASF GitHub Bot commented on NIFI-4250:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2045
Don't worry about the ANTLR stuff, that seems to trip up Travis sometimes.
I can review this either this weekend or early next week. One quick question is
whether you think it would be too confusing for the user to just add "delete"
as an operation to PutElasticsearch(5), it would require doc updates and such.
I'm just thinking that after one version of a Delete ES processor is available,
the rest would be desired, requested, and possibly implemented. If that were
the case, would it be better to have 3 new processors for delete, or to update
the 3 Put processors to accept delete? I'm not leaning one way or the other,
I'm interested in your thoughts and others' in order to provide the best user
experience.
> Create support for deleting document by id from elasticsearch 5
> ---------------------------------------------------------------
>
> Key: NIFI-4250
> URL: https://issues.apache.org/jira/browse/NIFI-4250
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 1.3.0
> Reporter: Mans Singh
> Assignee: Mans Singh
> Priority: Minor
> Labels: delete, elasticsearch
>
> Create a processor to delete documents from elasticsearch 5 based on document
> id.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
