Github user henryr commented on the issue:

    https://github.com/apache/spark/pull/21070
  
    Ok, thanks for the context. I've worked on other projects where it's 
sometimes ok to take a small risk of a perf hit on trunk as long as the 
community is committed to addressing the issues before the next release. If the 
norms here are not to absorb any risk on trunk, that also seems reasonable.


---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to