kacpermuda commented on issue #58386: URL: https://github.com/apache/airflow/issues/58386#issuecomment-3551704056
Thanks @vikrantpuppala , that's good to hear. > It seems a bit odd to have it breaking by the client BTW. it seems still like a bug if they release client that is broken temporarily for some people - and it requries to enroll. Maybe we should limit it temporarily and open an an issue with databrick that this is not fixed and so that they let us know when it's all generaly available so that we can remove it ? WDYT? I do not know how long it can take and how disruptive it is, but IMHO this is wrong to have something that fails if your account is not enrolled to private beta. Fully agree @potiuk , should be an opt-in, but I can also understand that it was hard to detect - AFAIU there was no `.autocommit` property on Databricks connection before, and Airflow was just doing `conn.autocommit=X` in DbApiHook that suddenly started to use the newly implemented setter from Databricks connection. So the client/connection just rolled out a new feature under a new property and did not expect that somebody was already calling `.autocommit`. It should probably not fail for those not enrolled, but I understand those that are enrolled wanted to test it with a client. -- 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]
