Lehel44 commented on PR #7644: URL: https://github.com/apache/nifi/pull/7644#issuecomment-1696561182
@mark-bathori, I conducted manual testing on the `PutZendeskTicket` processor and the `ZendeskRecordSink` service. In both basic and advanced scenarios using RecordPath, both components demonstrated effective functionality. I observed two rooms for improvement during testing: Logically, a sink service doesn't seem to align well within a processor package. Even if both are located in the same NAR, it could be valuable to organize these modules into distinct common, processors, and services sections for improved clarity. (summon @turcsanyip) To further enhance the sink, it might be beneficial to implement a caching mechanism within the sink service. This would be particularly relevant in situations where there are numerous identical bulletins in the `BulletinRepository`. In such cases, if the `QueryNifiReporting` task runs with the `ZendeskRecordSink`, it could potentially create multiple identical tickets. Implementing a cache could mitigate this redundancy. -- 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]
