Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/16818
ping @hvanhovell
---
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/16818
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/16818
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/78498/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16818
**[Test build #78498 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78498/testReport)**
for PR 16818 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16818
**[Test build #78498 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/78498/testReport)**
for PR 16818 at commit
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/16818
Could you bring this up-to-date? @uncleGen
---
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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/16818
cc @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/16818
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72911/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16818
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/16818
**[Test build #72911 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72911/testReport)**
for PR 16818 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16818
**[Test build #72911 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72911/testReport)**
for PR 16818 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16818
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72844/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16818
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/16818
**[Test build #72844 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72844/testReport)**
for PR 16818 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16818
**[Test build #72844 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72844/testReport)**
for PR 16818 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16818
Merged build started.
---
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/16818
Merged build triggered.
---
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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/16818
cc @hvanhovell and @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
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16818
cc @gatorsmile also
---
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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/16818
cc @cloud-fan @hvanhovell
---
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/16818
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72574/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16818
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/16818
**[Test build #72574 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72574/testReport)**
for PR 16818 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16818
@uncleGen could you undo the changes to the WindowFrame's and the
BoundOrdering classes? Just change createBoundOrdering and make it convert the
long to an int for row frames (after checking
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16818
**[Test build #72574 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72574/testReport)**
for PR 16818 at commit
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16818
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/16818
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72571/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16818
**[Test build #72571 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72571/testReport)**
for PR 16818 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16818
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/16818
**[Test build #72571 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72571/testReport)**
for PR 16818 at commit
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16818
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/16818
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/16818
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72569/
Test FAILed.
---
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16818
cc @cloud-fan also
---
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 uncleGen commented on the issue:
https://github.com/apache/spark/pull/16818
@hvanhovell After dug deeply into code, I found the range scale has nothing
to do with `RowBuffer`, so there is no need to limit this to allowing long
values for range frames only, and this pr
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16818
**[Test build #72569 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72569/testReport)**
for PR 16818 at commit
Github user valek commented on the issue:
https://github.com/apache/spark/pull/16818
> Just make sure we can construct a range frame that respects longs, and
throw an error for row frames.
This seems totally reasonable
---
If your project is set up for it, you can reply to
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16818
@hvanhovell Thanks for your suggestions, it is just what I failed to notice
or consider.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16818
@uncleGen I think we should limit this to allowing long values for range
frames only; row frames should not get larger than `1 << 31 + 1`. The reason
for this is that we also need to be able to
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16818
cc @srowen
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16818
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72432/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16818
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/16818
**[Test build #72432 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72432/testReport)**
for PR 16818 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16818
**[Test build #72432 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72432/testReport)**
for PR 16818 at commit
44 matches
Mail list logo
