[
https://issues.apache.org/jira/browse/MINIFICPP-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703210#comment-16703210
]
ASF GitHub Bot commented on MINIFICPP-479:
------------------------------------------
Github user phrocker commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/453
Thanks for submitting this. I think there is definite overlap between work
I previously had with MINIFICPP-479
(https://github.com/apache/nifi-minifi-cpp/compare/master...phrocker:MINIFICPP-479?expand=1)
I collected commits from across computers and squashed them, but has the side
effect that it does validation at flow file load time ( something we've
desperately needed) -- giving us a much earlier failure. a bit different
implementation -- and it informs c2 of java validators to be used.
what is the motivation of this PR beyond that work that we discussed
offline? I think the same "pros" exist for both works. That work has been
around since June -- so it's probably stale in its ideas, so I'll take a look
at this at some point. Thanks again.
> Incorporate property validation information into manifest
> ---------------------------------------------------------
>
> Key: MINIFICPP-479
> URL: https://issues.apache.org/jira/browse/MINIFICPP-479
> Project: NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: Andrew Christianson
> Assignee: Andrew Christianson
> Priority: Major
>
> High-level intent is to avoid round-trip to c2 to know that flow is valid
> (or, invalid in common/trivial ways).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
