nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Dyer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-4332) Add NiFi Shell for interacting with NiFi REST API
Date Fri, 08 Sep 2017 18:14:02 GMT

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

Jeremy Dyer commented on NIFI-4332:
-----------------------------------

[~bbende] I think you and I are thinking close along the same line here. Slight difference
I was thinking, beyond having just the nifi-client-dto, to have a small implementation that
also already had the HTTP library implemented as well. Maybe thinking of this more like a
service implementation? So users could simple invoke a single method and receive a response
without having the program all of the HTTP interactions.

As for the shell part I'm really impartial about how it is implemented but do agree that having
multiple languages would be a burden. I think at a minimum some sort of shell wrapper as you
linked above which in turn called this "client' would be handy to even further save users
from even having to write code to interact with the client.

> Add NiFi Shell for interacting with NiFi REST API
> -------------------------------------------------
>
>                 Key: NIFI-4332
>                 URL: https://issues.apache.org/jira/browse/NIFI-4332
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Jeremy Dyer
>            Assignee: Jeremy Dyer
>
> There are several permutations of nifi shells floating around on Github. The fact that
so many of these exists tells me its a feature people want. I propose we add a NiFi shell
to the official project that people can use for official interaction with the NiFi REST API.
While shells are typically not written in Java I feel quite strongly in our case using Java
would be the best fit. Using Java would allow us to use reflection on the "nifi-web-api" layer
to reflected expected types, paths, responses, etc with minimal coding effort.
> I expect there will be many more features that can be added to this shell but as a minimal
starting point the shell should allow an end user to interact with all of the NiFi REST API
endpoints defined at https://nifi.apache.org/docs/nifi-docs/rest-api/index.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message