Github user robbinspg commented on the issue:
https://github.com/apache/spark/pull/16841
OK I'll raise a separate Jira, document the differences and submit a 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
Github user kevinyu98 commented on the issue:
https://github.com/apache/spark/pull/16841
@gatorsmile sure, I will do that. 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
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16841
To make the results consistent between big endian and small endian, we can
improve the queries with the extra order by clauses.
@robbinspg Which queries failed? @kevinyu98 Can you
Github user kevinyu98 commented on the issue:
https://github.com/apache/spark/pull/16841
Hello Pete: Thanks for running the test case. Can you send the failing test
case file to me? Also I can provide new test files with the output files, can
you help test on your platforms? thanks.
Github user robbinspg commented on the issue:
https://github.com/apache/spark/pull/16841
@kevinyu98 Several of the new tests fail on Big Endian platforms. It
appears that rows are returned in a slightly different order but are still a
correct output from the query. For example
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16841
LGTM
---
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/16841
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72984/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16841
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16841
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/16841
**[Test build #72984 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72984/testReport)**
for PR 16841 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16841
**[Test build #72984 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72984/testReport)**
for PR 16841 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16841
ok to test
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16841
test 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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16841
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/16841
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/16841
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/72833/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16841
**[Test build #72833 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72833/testReport)**
for PR 16841 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16841
**[Test build #72833 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/72833/testReport)**
for PR 16841 at commit
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16841
test 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 so,
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/16841
OK to test
---
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/16841
Can one of the admins verify this patch?
---
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
21 matches
Mail list logo
