[
https://issues.apache.org/jira/browse/MINIFICPP-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581123#comment-16581123
]
Aldrin Piri commented on MINIFICPP-598:
---------------------------------------
I am not exactly sure what you mean by "these relationships". I believe your
thought process is that there are actual relationships that are on the agent
that would be transmitted? I could see this from the metrics/heartbeat
perspective but believe we do not, from the agent, know what the relationships
actually are for a processor, just that there are the capacity for zero or more
of them to exist. The manifest is simply a recipe book for how someone could
build a flow for it.
This is the place I am coming from when I talk about the strategies. For the
case of RouteOnAttribute (ROA), I could imagine a strategy named something akin
to "Dynamic Property Key Mapped." For this strategy, and someone that was
trying to use this to drive a design process, could then evaluate all the
properties and enumerate equivalent relationships. Another strategy would be
that used by NiFi's distribute load which would simply be "Number" which might
reference the specific property carrying this information.
Let me know if this clarifies things a bit or if I am not thinking about this
in the right way.
> Add supported relationships to agent manifest
> ---------------------------------------------
>
> Key: MINIFICPP-598
> URL: https://issues.apache.org/jira/browse/MINIFICPP-598
> Project: NiFi MiNiFi C++
> Issue Type: Bug
> Reporter: Mr TheSegfault
> Assignee: Mr TheSegfault
> Priority: Major
>
> Probably need to include the relationship name and description
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
