Github user HandOfGod94 commented on the issue:
https://github.com/apache/nifi/pull/1294
Hi @alopresto,
Noob's opinion. (Seriously, I am noob and am open for suggestions/advice):
I am honestly not satisfied with the way I have done things. I initially
continued with it as NiFi design guidelines said to have independent processor
implementation, but as I proceeded I found the predefined classes are still not
closed for modification and in order for things work I had to modify them,
which eventually led to buggy implementation.. Do you think we should redesign
whole EncryptProcessors? I was thinking having a common entry point for
encryption of content as well as attributes, but this would break backward
compatibility (not sure). Again it's noob's opinion, I would like to hear about
your thoughts on this.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
