Github user jdye64 commented on the issue:
https://github.com/apache/nifi-minifi-cpp/pull/37
@apiri I agree. That was my intent was to allow each Processor itself to
determine how/if it used the dynamic properties that was the reason for
creating the new set in Processor.cpp for the dynamic properties instead of
just lumping them all into the same "supportedProperties" set. The only reason
for the framework "switch" was just since the CPP version is meant to run on
embedded and lightweight hardware maybe the guard against preventing someone
from flooding the yml flow with so many dynamic properties that the embedded
device ran out of memory and crashed.
I see your point and in my own shallow mind I thought that was what I was
trying to do but maybe your right and this implementation doesn't make sense?
What were you thinking?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
