Github user aray commented on the issue:

    https://github.com/apache/spark/pull/18786
  
    I'm pushing for it to stay as is because it's the more logical layout of 
the data: min=0%, 25%, 50%, 75%, max=100%. It's also more consistent with 
summary of native R dataframes (and for Python the Pandas describe method).
    
    Anyone who is accessing these fields blindly by index should know they are 
taking a risk. Furthermore we already cast everything to strings for the output 
of summary so it should be obvious that it's not meant for reuse.
    
    @felixcheung If you still feel strongly a compromise might be to print a 
warning when `summary` is called from R with no additional arguments.


---
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