Arpad Boda created MINIFICPP-991:
------------------------------------
Summary: Handling environment vars in MiNiFi
Key: MINIFICPP-991
URL: https://issues.apache.org/jira/browse/MINIFICPP-991
Project: Apache NiFi MiNiFi C++
Issue Type: Improvement
Reporter: Arpad Boda
Assignee: Arpad Boda
As [~phrocker] pointed out in
[https://github.com/apache/nifi-minifi-cpp/pull/612] env var setting might
caused unintended behaviour in case multiple processors (for eg. a cpp and a
Python one) try to set and use the same env var, which is a valid case for
oepncv.
We should find a general approach of handling env vars:
* If we handle them in processor init phase, that's guaranteed to be thread
safe, but property values are not accessible in that phase, so configuration is
difficult
* Handling in onschedule phase allows access to properties, although we have
to deal with thread-safety.
* No matter what approach we choose, a recommended way of doing this should be
documented to avoid users experiencing unwanted behaviours.
[~le.nghia] [~bakaid] [~phrocker] please share your opinions!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
