[
https://issues.apache.org/jira/browse/MINIFICPP-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16581116#comment-16581116
]
Mr TheSegfault commented on MINIFICPP-598:
------------------------------------------
When making this ticket I looked at route on attribute since that was the one
with the greatest concern ( at this time ). My first thought was that these
supported relationships would likely be transferred in the manifest. These
relationships will come with a description of "Dynamic Route". I'm not sure we
can do much more than define these dynamic routes that are dynamic.
i'm curious what you mean by "dynamic route strategies." This implies some type
of structure to routes. I'm likely missing something -- doesn't seem like
something the agent could infer when sending the manifest.
In my head my thought was 1) define a path for these relationships to be
delivered. If the consumers can infer relationships from dependent properties
that's great, but they're basically doing the work of RouteOnAttribute to some
degree. As a result the biggest bang for the buck is to delivery the
relationship name and description for the time being to help tease out how we
can make this work from a consumer's standpoint.
> 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)
