potiuk commented on PR #66952: URL: https://github.com/apache/airflow/pull/66952#issuecomment-5090619585
> Hello @gopidesupavan @potiuk , This PR is in charge of me not in @olegkachur-e. I was on vacation last two weeks and could not respond on comments and fixed merge conflicts in the current PR. Yesterday I fixed merge conflicts and as I see your guys in the evening added additional changes to the code. Could you please clarify for me should I continue to work on this PR or it is not on my duty anymore? Hello @MaksYermak - sorry for not responding before - I've been sick/out of action for the last week or so and slowly getting back to regular involvement. I tried to see - similarly as @gopidesupavan to fix the dependency issue, but as @eladkal noted - fixing betterproto to 6 years old pre-release version is a bad idea. Really the issue is on beam side not ours, so it's up on them to fix it. Luckily - they already did - it just did not make it into 2.75.0 release in July and it is planned to be released at the beginning of August. And this is the right way of solving the problem - and opens the way to un-suspend beam provider - making any workarounds on our side is just not something we should accept - especially that there is a fix in sight. You can read more details in here, where I wrote message to the dev team of Apache Beam: https://lists.apache.org/thread/lnm2gszq3lvqxgz70rms7zqmr757w5ol So - at this stage, what we need to do is to wait until 2.76.0 is released by Apache beam. Once this is done (+3 days cooldown on our side) - you should just rebase/resolve issues, bump min version for it pyproject.toml of the beam provider and all issues **should** be solved. I think a good idea for you might be to respond to that message if you feel that Beam team should speed it up a bit maybe - explaining how much needed it is by the composer team - and Google customers. Yes. I know it's frustrating, but it's really not something we should fix or workaround here. -- 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]
