Github user jtstorck commented on the issue:
https://github.com/apache/nifi/pull/1148
@mauriziocolleluori I've cherry-picked your commits into my branch, and
will be submitting a PR that includes your commits along with mine (for
Github user mauriziocolleluori commented on the issue:
https://github.com/apache/nifi/pull/1148
@trixpan @pvillard31 thank you for you comments. I will look into the Kafka
processors and revert back once it's done.
---
If your project is set up for it, you can reply to this email
Github user trixpan commented on the issue:
https://github.com/apache/nifi/pull/1148
@mauriziocolleluori thank you for the contribution.
any intent on addressing @pvillard31 's comment? While a positive answer is
more than welcome, a negative answer is also welcome... all we
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/1148
Hi @mauriziocolleluori,
If you still encounter issues in UI when testing properties while using
expression language, please check that nifi.kerberos.krb5.file is correctly set
in your
Github user mauriziocolleluori commented on the issue:
https://github.com/apache/nifi/pull/1148
I have recompiled and added expression language support (with expected
evaluation on read) for both principal and keytab. However when I add any
expression language to one of such
Github user mauriziocolleluori commented on the issue:
https://github.com/apache/nifi/pull/1148
Thank you for your feedback, I will add the necessary call to
evaluateAttributeExpressions() and submit a new pull request.
---
If your project is set up for it, you can reply to this
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/1148
Thank you for contributing. In addition to adding the
expressionLanguageSupported flag on the property descriptors, we would also
need to go through the code and find every place where the properties
