Longterm Development #131
Description
The solution is great, combining important functionalities of Databricks platform.
Can I please have some questions for long term usage?
- Let's imagine that, 1 year later, Databricks releases new versions of the databricks-sdk and mlflow.
- How can this repository support different API versions? Saying Databricks SDK releases a new version on a day, then developers need to change this code to handle the new logic of the new Databricks SDK versions.
- How long does it take to release new versions that support the latest Databricks SDK but still support the legacy version?
- How can end users (I suppose developers) switch flexibly between 2 versions of Databricks SDK?
Just some of my stupid questions ...