jason810496 commented on PR #54651: URL: https://github.com/apache/airflow/pull/54651#issuecomment-3228001608
> I think we need to discuss and approach a deprecation mechanism for it. I would be for a rather "clean cut" with this one than a long deprecation. I see no particular reason to stick to the old mechanism if we convert all our message queue providers to the new versions. Agree. I will vote for "Sudden death" approach in this case and have same though as this `Those are still very early days for message queue, and i bet not many people have already built their own queues, and even if they did, switching to the new API is very straightforward.` part. Additionally, having "Sudden death" is more clean because replacing Queue URI with Scheme is more like a fix but also a breaking change IMO. _If_ we decide to go with "Sudden death", does it mean we need to remove the compatible interface for common queue? Like the following part can be directly removed? ( Since there will be no more `queue` parameter in 2.0.0 ) https://github.com/apache/airflow/pull/54651/files#diff-9eba0f966907dc13a12fae086fff750db6a51fffc60275fdddbea41227fb6dd8R68-R80 > you will not be able to downgrad amazon, kafka, redis selectively By the way, only SQS and Kafka will be impacted, since Queue Provider of Redis haven't been released before. It was excluded in last provider release. -- 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]
