At a glance, it doesn't seem so. That is a corner case in two ways - very
old dates and using RDDs, at least it seems.
I also suspect that individual change is tied to a lot of other date
related changes in 3.2, so may not be very back-portable.
You should pursue updating to 3.2 for many reasons,
it looks that this commit (
https://github.com/apache/spark/commit/a85490659f45410be3588c669248dc4f534d2a71)
do the trick.
[image: image.png]
Don't you think, this bug is enough important to incluide in 3.1 branch?
Regards
El jue, 20 ene 2022 a las 8:55, Gaspar Muñoz ()
escribió:
> Hi guys,
>
Hi guys,
hundreds of spark jobs run on my company every day. We are running Spark
3.1.2 and we want enable Adaptive Query Execution (AQE) for all of them.
We can't upgrade to 3.2 right now so we want enable it explicitly using
appropriate conf when spark submit.
Some of them fails when enable
