exceptionfactory commented on pull request #5324: URL: https://github.com/apache/nifi/pull/5324#issuecomment-1036490305
Thanks for the reply @markobean, I can see why adding a specific processor takes us further down a road that is not ideal, as others have already stated. Without wanting to complicate things further, the character set encoding is a concern, requiring an additional optional property. From a maintenance point of view, it is much easier to deprecate an entire component, as opposed to a property. Adding this feature, even with warnings and documentation, locks in future support for a long period of time. I would much rather see that in a separate processor, even given the discussion thus far. If the concern is that it makes the capability too obvious, then that goes against introducing the feature in this processor. In absence of other reasons for supporting this feature in this processor, I am still not inclined to move forward as it stands. -- 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]
