nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mattyb149 <>
Subject [GitHub] nifi issue #2045: NIFI-4250 - Elasticsearch 5 delete processor
Date Sat, 12 Aug 2017 20:48:10 GMT
Github user mattyb149 commented on the issue:
    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.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message