rusackas commented on PR #42192: URL: https://github.com/apache/superset/pull/42192#issuecomment-5013135712
The bump itself was fine, but pandas 2.2+ silently drops support for SQLAlchemy < 2.0. When it sees our 1.4 it pretends SQLAlchemy isn't installed, treats engines like raw DBAPI connections, and falls back to a sqlite-only code path, which is why every to_sql/read_sql call site went red (uploads, example data loading, annotation layers, filter values, the test data loaders). The pandas SQL layer itself still runs fine on 1.4, so I pushed a small shim that lowers pandas' advertised minimum back to the 2.1-era value at import time. It's a no-op once we're on SQLAlchemy 2 and can be deleted when that migration lands. The License Check failure was just the RAT jar download flaking, a re-run should fix it. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
