Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18974
Hi, All.
Two more Arrow releases seem to be out. How about the Python side? Can we
catch up some?
- 0.7.1 (1 October 2017)
- 0.7.0 (17 September 2017)
---
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18974
Thank you for comments. I understand issues regarding Jenkins interaction
in the Python side. I close this PR for now since the Python side is not ready
for upgrading Arrow.
---
If your project is
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/18974
as with @rushing my primary concern with the upgrade here is the Jenkins
interaction of when we eventually need to upgrade th Python side as well. It
seems like we might not need to yet for 0.6.0
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/18974
Do we need to upgrade pyarrow in Jenkins environment?
LGTM except for it.
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/18974
I'm ok with it if arrow 0.6.0 doesn't introduce new dependencies.
---
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
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18974
I agree with the usage of the latest one.
It would be good to periodically update a library if the library does not
introduce drastic change (e.g. changing APIs) for ensuring stability for a
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/18974
According to #18459, I'm pining @holdenk and @cloud-fan , too.
---
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
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/18974
Thanks for this @kiszk. I was thinking we would need to do an upgrade for
DecimalType support. I'm going to help out with that on the Arrow side, but it
still might not be ready until 1 or 2
Github user kiszk commented on the issue:
https://github.com/apache/spark/pull/18974
ping @srowen @ueshin @BryanCutler
---
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/18974
ping @srowen @ueshin @BryanCutler
---
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/18974
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/18974
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80799/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18974
**[Test build #80799 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80799/testReport)**
for PR 18974 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18974
**[Test build #80799 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80799/testReport)**
for PR 18974 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18974
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/18974
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80797/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18974
**[Test build #80797 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80797/testReport)**
for PR 18974 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18974
**[Test build #80797 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80797/testReport)**
for PR 18974 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18974
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/18974
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80795/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18974
**[Test build #80795 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80795/testReport)**
for PR 18974 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/18974
**[Test build #80795 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/80795/testReport)**
for PR 18974 at commit
22 matches
Mail list logo
