Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15907
Merging in master/branch-2.1
---
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/15907
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/15907
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68855/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15907
**[Test build #68855 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68855/consoleFull)**
for PR 15907 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15907
**[Test build #68855 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68855/consoleFull)**
for PR 15907 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15907
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/15907
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68821/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15907
**[Test build #68821 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68821/consoleFull)**
for PR 15907 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15907
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68820/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15907
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/15907
**[Test build #68820 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68820/consoleFull)**
for PR 15907 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15907
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68819/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15907
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/15907
**[Test build #68819 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68819/consoleFull)**
for PR 15907 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15907
**[Test build #68821 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68821/consoleFull)**
for PR 15907 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15907
**[Test build #68820 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68820/consoleFull)**
for PR 15907 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15907
**[Test build #68819 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68819/consoleFull)**
for PR 15907 at commit
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/15907
Looks good
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15907
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68798/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15907
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/15907
**[Test build #68798 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68798/consoleFull)**
for PR 15907 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15907
**[Test build #68798 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68798/consoleFull)**
for PR 15907 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15907
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/15907
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68793/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15907
**[Test build #68793 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68793/consoleFull)**
for PR 15907 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15907
**[Test build #68793 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/68793/consoleFull)**
for PR 15907 at commit
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/15907
It would be good.
In that case, is it better to insert explicit cast (from int to long) if a
caller gives an int variable? This is why we want to explicitly express a
specification of public
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15907
I'm thinking 2. What do you think?
---
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 kiszk commented on the issue:
https://github.com/apache/spark/pull/15907
Ideally, it is a good idea. Do you want to do that change using this PR?
Another question is which scope do we apply such a change?
(1) Only in methods that I applied changes to.
(2)
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/15907
Yea it might be a good idea to just use longs.
---
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
30 matches
Mail list logo
