Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/22144
I think this is different from the blocker tickets we opened before. We
should try our best to avoid accidentally dropping the existing support. Please
encourage more people in the community to try our RCs and find out all the new
regressions or bugs.
During the RC stage, for the new regressions, we can either fix it if the
fix is very safe/tiny; or revert the PRs that introduce the regressions. This
is how we handle the regressions during the RC stage.
For this specific case, I do not think the root cause is found. If we
revert the previous PRs https://issues.apache.org/jira/browse/SPARK-18186 that
were merged in 2.2 release, it could easily introduce new regressions. Thus, we
normally do not revert the PRs that were merged in the previous releases.
Please add it as a known issue in the release note.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
