Github user tgravescs commented on the issue:

    https://github.com/apache/spark/pull/22112
  
    we should pull this back into spark 2.3 at least, I don't think this is a 
clean cherry pick due to barrier scheduling stuff, would you be willing to put 
up PR?


---

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

Reply via email to