Github user holdenk commented on the issue:

    https://github.com/apache/spark/pull/17831
  
    Thanks for making this PR with the details @gatorsmile it appears to be 
orthogonal to this change. Historically we've treated Python API parity fixes 
as closer to bug fixes rather than new features which is why I was thinking 
this made sense for 2.2, but I'll defer to your expertise in SQL and we can 
just target this for master.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to