Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12552
---
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 feature is
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12552#issuecomment-212848295
Merged to master/1.6 (quite safe update; may get a bug fix)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/12552#issuecomment-212744081
@HyukjinKwon thanks for picking up this PR & taking the time to investigate
the places where the changes could be useful for Spark. This looks good to me
as well.
Github user lresende commented on the pull request:
https://github.com/apache/spark/pull/12552#issuecomment-212730550
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12552#issuecomment-212715214
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12552#issuecomment-212715213
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12552#issuecomment-212715085
**[Test build #56454 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56454/consoleFull)**
for PR 12552 at commit
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12552#issuecomment-212690085
@JoshRosen Sure.
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/12552#issuecomment-212686487
Mind adding "closes #11847" in your PR so that the other one will
automatically be closed when this one is merged?
---
If your project is set up for it, you can
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12552#issuecomment-212683405
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
Github user HyukjinKwon commented on the pull request:
https://github.com/apache/spark/pull/12552#issuecomment-212683370
This was proposed in https://github.com/apache/spark/pull/11847 (upgrade to
`2.9.2`) before but since it looks the PR is abandoned without a JIRA and with
a PR not
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12552#issuecomment-212683124
**[Test build #56454 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56454/consoleFull)**
for PR 12552 at commit
GitHub user HyukjinKwon opened a pull request:
https://github.com/apache/spark/pull/12552
[SPARK-14787][SQL] Upgrade Joda-Time library from 2.9 to 2.9.3
## What changes were proposed in this pull request?
https://issues.apache.org/jira/browse/SPARK-14787
The possible
13 matches
Mail list logo
