nandorsoma commented on PR #7045: URL: https://github.com/apache/nifi/pull/7045#issuecomment-1600646995
@zhangzhonglai, a little addition to what @ChrisSamo632 said. In NiFi, we prefer solutions when we can do explicit configuration. It is easier to test, features are more apparent, less documentation is needed, and most of the time it involves less surprise. However, there are more and more libraries that do some kind of "automagic", but we need to integrate them into NiFi. The main issue is that they are not designed in mind that they need to be part of a framework. Though our goal is to make them feel native to NiFi. If it can be done via workaround, so be it. That was my general take on the topic. Regarding #5775. We can reference environment variables in properties with expression language, so the PR might work for you without the extra library. For that, we need to set the `ExpressionLanguageScope` of the property to anything other than `NONE`. Preferably to `FLOWFILE_ATTRIBUTES`. Could you test that the PR mentioned solves your issue? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
