[
https://issues.apache.org/jira/browse/MINIFICPP-673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16858517#comment-16858517
]
Mr TheSegfault commented on MINIFICPP-673:
------------------------------------------
[~mshareef] Strictly speaking ECU is a concept is defined in this epic. The sub
tasks ( which should be issues in the EPIC, my apologies ) define those
implementations. The first, log collector is defined in
https://issues.apache.org/jira/browse/MINIFICPP-621. Let me know if you have
any questions.
> Define ECU (Edge Collector Unit )
> ---------------------------------
>
> Key: MINIFICPP-673
> URL: https://issues.apache.org/jira/browse/MINIFICPP-673
> Project: Apache NiFi MiNiFi C++
> Issue Type: Epic
> Reporter: Mr TheSegfault
> Assignee: Murtuza Shareef
> Priority: Major
> Labels: ECU, nanofi
> Fix For: 0.7.0, 0.8.0
>
>
> Edge Collector Units ( ECU ) will be minimized agents whose sole focus is
> collection and retrieval of data. Defined as feature facing constructs, ECUs
> will define functionality that is agnostic of system. We'll build the
> portability behind the library.
>
> [~aboda] This ticket encompasses building software from individual units of
> functionality. So take the log aggregation example in MINIFICPP-621 . There
> we have an instance of "tail file" linked to site to site. To do this will
> require the ability to link these units ( we've called them building blocks,
> but that's more documentation ), stream data between them, and then define
> success and failure conditions ( or relationships ).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
