Github user rdblue commented on the issue:
https://github.com/apache/spark/pull/19448
I have a lot of sympathy for the argument that infrastructure software
shouldn't have too many backports and that those should be generally bug fixes.
But, if I were working on a Spark distribution at a vendor, this is something I
would definitely include because it's such a useful feature. I think that by
not backporting this, we're just pushing that work downstream. Plus, the risk
to adding this is low: the main behavior change is that users can specify a
previously-banned committer for Parquet writes. Is it a bug fix? Probably not.
But it fixes a big blocker.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
