Github user srowen commented on the issue:
https://github.com/apache/spark/pull/22144
So, some particular functionality worked in Spark 2.1, but didn't work
starting in 2.2. If anything, that was the breaking change. (I wonder if it was
on purpose, or documented, but, what's done is done in any event.) Dropping
support for something in a minor release isn't crazy though.
But it doesn't work in 2.2 or 2.3. I don't see that it has to work in 2.4,
right?
I understand it impacts a user and was reported a long time ago, but, so
were 100 other things.
Consider the broader context of the release cycle, no I do not think this
should block 2.4.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
