Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/21427
yea, I generally agree with that and I feel in the same way. I think I had
a talk about this @gatorsmile and @cloud-fan multiple times. Here is my
thought: we should not make a configuration only because it's going to break
something. We should see if that usage makes sense, it's a bug or not,
workaround is easy, the API is experimental or evolving and it's trivial or not.
My concern is having too many configurations to control each behaviour for
every behaviour change regardless of thinking other options.
I kind of am still okay with having a configuration in most cases but think
about the current behaviour, proposed change and what change we need to have a
configuration.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
