tpalfy commented on PR #10538: URL: https://github.com/apache/nifi/pull/10538#issuecomment-3724898818
"The question now is whether one Processor should continue to support a significantly different use case, or whether a separate Processor provides an understandable way forward." I think that's a fair and good question. I also think it warrants a cost-benefit analysis. I would consider 2 major concerns: UX and DevX. As for UX, there is value in encompassing the functionality of "consume from kafka" in a single entity and having the "how exactly" covered by configuration. Otherwise, the line between "similar" and "significantly different" use-case can get blurry. As for DevX, while I see the value of extension vs modification, the new processor would basically have the same SDLC as the current one. Whatever change is needed, it would be needed for both, most, if not all, of the time. That screams bad design. This is not a new feature. It has it's risks, but it's not something that we have nothing but prediction to rely on. We have a history of this in the previous implementation. Again, maybe I missed something, but as far as I can tell - specifically from maintenance perspective - it was fine because the logic is well isolated enough. -- 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]
