Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16361
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 so,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16361
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16361
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71088/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16361
**[Test build #71088 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71088/testReport)**
for PR 16361 at commit
[`df3a852`](https://github.com/apache/spark/commit/d
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16361
LGTM pending Jenkins. Thanks!
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16361
**[Test build #71088 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71088/testReport)**
for PR 16361 at commit
[`df3a852`](https://github.com/apache/spark/commit/df
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16361
Merged build finished. Test FAILed.
---
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16361
**[Test build #70838 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70838/testReport)**
for PR 16361 at commit
[`c2de5ee`](https://github.com/apache/spark/commit/c
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16361
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70838/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16361
**[Test build #70838 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70838/testReport)**
for PR 16361 at commit
[`c2de5ee`](https://github.com/apache/spark/commit/c2
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16361
Jenkins, retest this please
---
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 w
Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16361
@cloud-fan, while I agree that the field names aren't really used here, I
don't think `patterns.scala` is the right place to fix this because it seems a
little dodgy to be picking a safe name way
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/16361
it seems to that the grouping key alias is only used for execution(logical
Aggregate node doesn't need grouping expression to be named), can we just alias
them with k1,k2, ... with avoid this prob
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16361
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70433/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16361
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16361
**[Test build #70433 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70433/testReport)**
for PR 16361 at commit
[`c2de5ee`](https://github.com/apache/spark/commit/c
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16361
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16361
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70432/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16361
**[Test build #70432 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70432/testReport)**
for PR 16361 at commit
[`b858204`](https://github.com/apache/spark/commit/b
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16361
**[Test build #70433 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70433/testReport)**
for PR 16361 at commit
[`c2de5ee`](https://github.com/apache/spark/commit/c2
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16361
**[Test build #70432 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70432/testReport)**
for PR 16361 at commit
[`b858204`](https://github.com/apache/spark/commit/b8
Github user brkyvz commented on the issue:
https://github.com/apache/spark/pull/16361
cc @joshrosen
---
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 t
22 matches
Mail list logo
