Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13909
thanks, merging 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
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/13909
I updated the benchmark result and generated code.
FYI: Since I update the benchmark result once with `UnsafeBufferWrite`, the
performance is almost same.
---
If your project is set up for it,
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/13909
LGTM
BTW, @kiszk have you updated the benchmark with newest change, especially
after the UnsafeArrayData change?
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70668/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
**[Test build #70668 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70668/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70668 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70668/testReport)**
for PR 13909 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13909
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 wishes
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70657/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70657 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70657/testReport)**
for PR 13909 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13909
yea we should! thanks for pointing this 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 have this
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/13909
@cloud-fan I rethought after changing `allowNull` to `isMapKey`, and
finally I see what you said.
And we should revert the error message changes 4a0409a, right?
---
If your project is set
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70640/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70636/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
**[Test build #70636 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70636/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70640 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70640/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70636 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70636/testReport)**
for PR 13909 at commit
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/13909
I see, I agree that we shouldn't block this pr.
---
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
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13909
Well I don't think we should waste time arguing this minor problem and
block this PR, how about we revert it and send a new PR to add it?
---
If your project is set up for it, you can reply to
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13909
I think the validation logic should be consistent across the system, you
can't add the null check in `CreateArray` just because it's easy to do.
Currently we do null check based on `nullable`
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/13909
@cloud-fan Hmm, I didn't mean we don't trust the source side.
Currently we DO validate the null regardless of `allowNull` value.
The difference by the `allowNull` is setting null or
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70614/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70614 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70614/testReport)**
for PR 13909 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13909
@ueshin That will be a big mess if we validate the null here and there, I
think we should only do it at the source side. If we do not trust the source
side, there are a lot of other places that
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/13909
@cloud-fan Hmm, I agree that it's guaranteed by the source, but I thought
that's why we should use `containsNull` for `allowNull` to guarantee the value
will not be null when `containsNull == false`
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13909
> Should use dataType.containsNull for allowNull?
no we shouldn't, `containsNull` is kind of an optimizing hint that
guarantees the value will not be null, and it's guaranteed by the
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70614 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70614/testReport)**
for PR 13909 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70608/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70608 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70608/testReport)**
for PR 13909 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70607/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
**[Test build #70607 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70607/testReport)**
for PR 13909 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70606/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
**[Test build #70606 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70606/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70608 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70608/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70607 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70607/testReport)**
for PR 13909 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13909
LGTM, pending jenkins
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70606 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70606/testReport)**
for PR 13909 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70584/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70584 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70584/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70584 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70584/testReport)**
for PR 13909 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70578/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70578 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70578/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70578 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70578/testReport)**
for PR 13909 at commit
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/13909
LGTM except for few minor comments.
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70570/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70570 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70570/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70570 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70570/testReport)**
for PR 13909 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70568/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70568 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70568/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70568 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70568/testReport)**
for PR 13909 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13909
LGTM, I left some comments about code style, thanks for working on it!
BTW, can you update the benchmark result? I think we have finalized the
solution now.
---
If your project is set
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70555/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70555 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70555/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70555 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70555/testReport)**
for PR 13909 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70545/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70545 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70545/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70545 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70545/testReport)**
for PR 13909 at commit
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/13909
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70540/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70540 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70540/testReport)**
for PR 13909 at commit
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/13909
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70537/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70537 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70537/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70537 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70537/testReport)**
for PR 13909 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70480/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
**[Test build #70480 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70480/testReport)**
for PR 13909 at commit
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/13909
@cloud-fan thank you for your comments. I implemented to create
`UnsafeArrayData` using `UnsafeRow`. I hope that this makes the creation
simpler.
---
If your project is set up for it, you can reply
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70480 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70480/testReport)**
for PR 13909 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13909
sorry for the delay. Yea looks like we can't reuse the byte array of unsafe
data in expressions, which may get cached expectedly and leads to wrong result.
I'm a little concerned about
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/13909
ping @cloud-fan
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70327/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70327 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70327/testReport)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70327 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70327/testReport)**
for PR 13909 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70013/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
**[Test build #70013 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70013/consoleFull)**
for PR 13909 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70013 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70013/consoleFull)**
for PR 13909 at commit
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/13909
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/70010/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/13909
**[Test build #70010 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/70010/consoleFull)**
for PR 13909 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/13909
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/13909
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69995/
Test PASSed.
---
1 - 100 of 273 matches
Mail list logo
