Hi @Albertino , how are you doing today?
Thanks for calling this out. as per my understanding, at the moment, the pandas pin is there intentionally. Databricks Connect release notes say supported pandas versions are currently limited to 1.0.5<=pandas<3 to avoid breakage in pyspark.pandas workloads after the pandas 3.0.0 release.
Fully agree that pandas 3 support will matter. It likely needs proper compatibility work across Databricks Connect and pandas API on Spark before the restriction can be lifted safely. Hopefully that lands soon.