[GitHub] [nifi] exceptionfactory commented on pull request #7231: [NIFI-2964] Added ability for AttributeToJSON to handle nested JSON when either outputting to a flow file or an attribute.

["exceptionfactory (via GitHub)" <gi...@apache.org>]

exceptionfactory commented on PR #7231:
URL: https://github.com/apache/nifi/pull/7231#issuecomment-1551830406

   > @exceptionfactory Sorry I have to retract my initial response. My team had a specific use case where they wanted to pick and choose what they wanted as JSON and what they wanted as escaped. The regex would allow for that. Although it does add complexity it does allow for keeping the current functionality intact. The property you suggested would either always treat attributes as JSON or always as escaped.
   
   Thanks for the reply @dan-s1. Based on that description, are you saying that there is a reason to keep some JSON values as escaped strings? That seems counter-intuitive in general, although every flow is different. The JSON output of AttributesToJSON can be modified using other Processors like JoltTransformJSON. Does translating all JSON attribute values into objects create processing problems in the use case mentioned?


-- 
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: issues-unsubscribe@nifi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org