featzhang commented on PR #27550: URL: https://github.com/apache/flink/pull/27550#issuecomment-3882865337
> I think we should not do this at all. I see that the current connector doc integration is not very smart and can be fragile, but manipulating tags here by some magical regex is complexity that I'm pretty sure will produce unexpected and faulty results, so I'd rather spare us from it. > > Regarding the problem that broke CI and shed light on this, I was a bit hasty about bumping the AWS doc version without verifying it locally, but I'd rather add these verification steps to the connector releasing docs. > > Edit: Connector release wiki updated [here](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=235835365#Creatingaflinkconnectorrelease-UpdateandproperlyintegratetheconnectordocumentationintheFlinkdocumentation(onlyforregularconnectorrelease,notflink-connector-parent)). Our approach will be two-fold: 1. **Mitigation at the Flink main project level** – we plan to introduce monitoring and guardrails in the primary Flink pipeline to prevent issues originating from the Connector project from breaking the entire workflow. This includes validation checks and defensive handling to isolate connector-related failures. 2. **Root cause resolution in the Connector project** – while adding protections upstream, we agree that the fundamental issue should be addressed within the Connector repository itself to prevent recurrence. The goal is to ensure pipeline stability at the platform level while still enforcing proper fixes at the source. -- 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]
