Hi All, I would like to start a discussion thread about the KIP-1144: Exposing a new public REST API for MirrorMaker2 <https://cwiki.apache.org/confluence/display/KAFKA/KIP-1144%3A+Exposing+a+new+public+REST+API+for+MirrorMaker+2>
This KIP introduces a new REST API tailored for MirrorMaker2 operational requirements. Tries to make the interaction with MirrorMaker2 easier by providing a new abstraction layer on top of Connect, that can hide the implementation details, and avoid managing the connectors directly. The original REST API implementation (before KIP-710 removed the complete public REST API) exposed the full Connect API, including features like creating, modifying and removing connectors, manipulating tasks. This is not only increased the operational complexity of MirrorMaker2 but allowed users to manipulate the underlying connect clusters in an unintended way, and also opened up attack vectors for malicious actors. This proposal introduces a set of REST endpoints for MirrorMaker2 to expose operational status and control information for replication flows. The design greatly reduce the amount of endpoints compared to the Connect REST API, and keep only the essential ones. Built on top of the Connect functionality, this KIP introduces new endpoints built specifically for MirrorMaker2 while applying the same BasicAuthSecurityRestExtension based on JAAS. With these endpoints, operators and tools can query the state of MirrorMaker2 deployments, enabling easier monitoring. I appreciate all your feedbacks and comments. Thank you, Berci -- *Bertalan Kondrat* ------------------------------
