GitHub user jdye64 opened a pull request:

    https://github.com/apache/nifi-minifi-cpp/pull/37

    MINIFI-171  Dynamic Properties support for processors

    Added support in Processor.cpp to both set and get dynamic properties.
    The logic will first attempt to set the parsed Property from the .yml
    file as a supported property. IF that parsed Property is not in the
    whitelisted supported list AND if the “nifi.accept.dynamic.properties”
    configuration is set to true then the Property will be added to a
    Map<String, Property> of dynamic properties that can be accessed in a
    manner similar to the supported properties from any processor logic
    that extends Processor.cpp

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jdye64/nifi-minifi-cpp MINIFI-171

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi-minifi-cpp/pull/37.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #37
    
----
commit 1d930fc3b9f3b228c567cc99b6d5617769491267
Author: Jeremy Dyer <jdy...@gmail.com>
Date:   2017-01-03T00:24:37Z

    MINIFI-171  Dynamic Properties support for processors
    
    Added support in Processor.cpp to both set and get dynamic properties.
    The logic will first attempt to set the parsed Property from the .yml
    file as a supported property. IF that parsed Property is not in the
    whitelisted supported list AND if the “nifi.accept.dynamic.properties”
    configuration is set to true then the Property will be added to a
    Map<String, Property> of dynamic properties that can be accessed in a
    manner similar to the supported properties from any processor logic
    that extends Processor.cpp

----


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to