Closed jasper-tms closed 10 months ago
Given that it's showing up while loading a pickle, I'm not 100% sure that this is an issue with pandas 1 vs 2, but rather the difference between the serverside version and the client version. That said, we need to do an overhaul of pyarrow serialization anyway and this is a good reminder.
We've made considerable progress towards upgrading our serialization approach to no longer have this issue. The server-side version is going to be pushed out in the next day or two and we're going to test the client changes a bit more before calling it good, since we need to have the server updates deployed first.
This issue should now be fixed with #114 / release 5.10.1.
In an environment with pandas v2.0.3 installed:
with:
Some googling suggests that this error is due to changes from pandas 1.x.x to pandas 2.x.x. That checks out, because if I downgrade to pandas v1.5.3, this
live_live_query
succeeds.I can't tell if this is something that pyarrow is doing wrong or CAVEclient is doing wrong, but you might consider marking
pandas<2.0.0
in your requirements, or investigating if you think this is a bug you could fix.