[ https://issues.apache.org/jira/browse/NIFI-4250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124743#comment-16124743 ]
ASF GitHub Bot commented on NIFI-4250: -------------------------------------- Github user mans2singh commented on the issue: https://github.com/apache/nifi/pull/2045 @mattyb149 Regarding having a separate delete processor - I prefer single responsibility principle since it avoids confusion and mixing up configuration, processing logic, error handling, testing, maintenance etc. Along the same lines ElasticSearch provides separate JAVA delete/put/get request builders. Besides, overloading put and delete is confusing to me from the REST semantics. Let me know your thoughts. > 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)