thomews commented on PR #11544: URL: https://github.com/apache/nifi/pull/11544#issuecomment-5477235599
Thanks for the feedback @exceptionfactory. We have already addressed the JSON API concern and switched from Jakarta JSON to Jackson. Regarding the configuration complexity, one possible direction would be to move the Kafka connection and Record Writer configuration into a separate KafkaRecordSink Controller Service and have the Reporting Task consume a RecordSinkService. This would simplify the Reporting Task configuration, while also separating the provenance reporting concerns from the Kafka-specific configuration. The question would be whether the Reporting Task should become destination-agnostic, since any RecordSinkService could then be selected. Do you think this would be a better fit for the concerns you raised around configuration complexity? -- 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]
