[
https://issues.apache.org/jira/browse/MINIFI-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15822597#comment-15822597
]
ASF GitHub Bot commented on MINIFI-171:
---------------------------------------
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?
> Dynamic Properties support for processors
> -----------------------------------------
>
> Key: MINIFI-171
> URL: https://issues.apache.org/jira/browse/MINIFI-171
> Project: Apache NiFi MiNiFi
> Issue Type: Improvement
> Components: C++
> Affects Versions: cpp-0.1.0
> Reporter: Jeremy Dyer
> Assignee: Jeremy Dyer
> Fix For: cpp-0.2.0
>
>
> Currently any Property read from the config.yml file that is not explicitly
> defined in the processor's implementation will be ignored by Processor.cpp
> when reading the configurations. This prevents any dynamic property from
> being defined in the config.yml and passed to the processor at runtime.
> Certain processors rely heavily on the concept of dynamic properties that are
> passed to them at runtime to handle things like setting dynamic properties
> based on properties that are declared. All of these possibilities cannot be
> handled upfront so there should be a mechanism, most likely in Processor.cpp,
> that allows for a list of dynamicProperties that are parsed form the
> config.yml file to be stored and accessed by the underlying processor
> implementation at runtime and use them as the processor desires.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
