Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/18786
merged to 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
Github user aray commented on the issue:
https://github.com/apache/spark/pull/18786
closing and reopening to trigger AppVeyor test that timed out
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18786
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18786
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80687/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18786
**[Test build #80687 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80687/testReport)**
for PR 18786 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18786
**[Test build #80687 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80687/testReport)**
for PR 18786 at commit
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
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/18786
I don't think it's a big deal either way, which is why I suggest to change
the order in Scala since it is new in Scala in this release, whereas it has
been in R for a few releases (or since the
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/18786
I suspect it is ok for R ...
---
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
Github user aray commented on the issue:
https://github.com/apache/spark/pull/18786
@rxin Any thoughts on whether it's ok to change the output of `summary` in
R in a non "additive" way?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/18786
Is it too late to change the Scala side output format? I suspect it doesn't
matter too much on Scala/Python which order they are in and preserving the
existing order in R could be helpful.
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/18786
I see. I recall the method name discussion; though changing API and/or
output format is something we generally want to avoid. Something like this has
been called out in past releases as we
Github user aray commented on the issue:
https://github.com/apache/spark/pull/18786
No the changes to `summary` are not additive, it inserts 25%, 50%, and 75%
percentiles before max (the last row). People that want the previous behavior
can use `describe`. Or if they are trying to
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/18786
@HyukjinKwon I'm not sure how - in AppVeyor we are building everything from
scratch... it does take time
---
If your project is set up for it, you can reply to this email and have your
reply
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/18786
@aray, it looks the tests with AppVeyor failed due to time limit, 1.5
hours. Would you mind closing and reopening this one to retrigger the test?
@felixcheung, It sounds now we are
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18786
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80120/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18786
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18786
**[Test build #80120 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80120/testReport)**
for PR 18786 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18786
**[Test build #80120 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80120/testReport)**
for PR 18786 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18786
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80091/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18786
Merged build finished. Test PASSed.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18786
**[Test build #80091 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80091/testReport)**
for PR 18786 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18786
**[Test build #80091 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80091/testReport)**
for PR 18786 at commit
23 matches
Mail list logo
