You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Aldrin Piri (JIRA)" <ji...@apache.org> on 2016/04/28 18:27:13 UTC
[jira] [Updated] (NIFI-1820) Establish Site to Site as an extension
point
[ https://issues.apache.org/jira/browse/NIFI-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aldrin Piri updated NIFI-1820:
------------------------------
Description:
Given NiFi's position to handle data, NiFi's efforts of dataflow could be supplemented and more versatile in supporting of various clients and systems with the means of extending Site to Site (S2S) with various implementations. Ultimately, this makes S2S an extension point.
In a broader context, it would be possible to provide remote input ports that can provide support for multiple protocols. In this case, the data would be the same, but may come across the "native" S2S socket protocol, HTTP, or other options.
This would require establishing core APIs which are currently available, and then varying implementations. Of course, dependent on transport mechanism, not all the semantics of site to site may not be supported, and an appropriate means should be made available to determine what is possible.
There would be various needs on top of this inclusive of some fairly extensive UI changes/additions to establish and express these conventions to the user, treating remote ports in a manner similar to processors/controller services.
was:
Given the NiFi's position to handle data, NiFi's efforts of dataflow could be supplemented and more versatile in supporting of various clients and systems with the means of extending Site to Site (S2S) with various implementations. Ultimately, this makes S2S an extension point.
In a broader context, it would be possible to provide remote input ports that can provide support for multiple protocols. In this case, the data would be the same, but may come across the "native" S2S socket protocol, HTTP, or other options.
This would require establishing core APIs which are currently available, and then varying implementations. Of course, dependent on transport mechanism, not all the semantics of site to site may not be supported, and an appropriate means should be made available to determine what is possible.
There would be various needs on top of this inclusive of some fairly extensive UI changes/additions to establish and express these conventions to the user, treating remote ports in a manner similar to processors/controller services.
> Establish Site to Site as an extension point
> --------------------------------------------
>
> Key: NIFI-1820
> URL: https://issues.apache.org/jira/browse/NIFI-1820
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Aldrin Piri
>
> Given NiFi's position to handle data, NiFi's efforts of dataflow could be supplemented and more versatile in supporting of various clients and systems with the means of extending Site to Site (S2S) with various implementations. Ultimately, this makes S2S an extension point.
> In a broader context, it would be possible to provide remote input ports that can provide support for multiple protocols. In this case, the data would be the same, but may come across the "native" S2S socket protocol, HTTP, or other options.
> This would require establishing core APIs which are currently available, and then varying implementations. Of course, dependent on transport mechanism, not all the semantics of site to site may not be supported, and an appropriate means should be made available to determine what is possible.
> There would be various needs on top of this inclusive of some fairly extensive UI changes/additions to establish and express these conventions to the user, treating remote ports in a manner similar to processors/controller services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)