Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/21598
I don't think it's too discretionary. We have a safeguard to control the
behaviour. Spark mentions it in the migration guide. In case of changing public
interface which breaks binary or source compatibility, there should really be
strong argument, sure. For clarification, I don't think such change is made
usually.
In this case, it changes a behaviour even with a safeguard. Sounds pretty
minor. I wonder why this is suddenly poped up. As I said, if the standards
don't reflect the practice, the standards should be corrected or the practice
should be complied. Committer's judgement is needed time to time. We need more
committers for the more proper review iteration. Let's back it roll.
If you prefer more conservative distribution, it should be an option to
consider using a maintenance release.
> we may choose to retain that buggy behavior
I strongly disagree. We should fix the buggy behavior. There's no point of
having upper versions.
If you strongly doubt it, please open a discussion in the mailing list and
see if we get agreed at some point.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
