Github user sureshthalamati commented on the issue:
https://github.com/apache/spark/pull/15192
Created PR to back port this fix to 2.1:
https://github.com/apache/spark/pull/17460
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user sureshthalamati commented on the issue:
https://github.com/apache/spark/pull/15192
sure. 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 feature
enabled and wishes so,
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15192
@holdenk Sure, we can backport it to Spark 2.1.
@sureshthalamati Could you please back port it to Spark 2.1?
---
If your project is set up for it, you can reply to this email and have y
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15192
Hi @gatorsmile , on the dev@ list someone asked if this was something we
were considering backporting into the 2.1 branch (for the 2.1.1 release). It
looks like it might be a reasonable candidate fo
Github user miketrewartha commented on the issue:
https://github.com/apache/spark/pull/15192
Thanks guys, this will be super, super helpful to us!
---
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 h
Github user sureshthalamati commented on the issue:
https://github.com/apache/spark/pull/15192
Thank you, @gatorsmile
---
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 gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15192
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 w
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15192
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71746/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15192
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15192
**[Test build #71746 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71746/testReport)**
for PR 15192 at commit
[`d8cbe54`](https://github.com/apache/spark/commit/d
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15192
LGTM pending test. The docker integration test cases pass in my local
computer.
However, I saw a not-related test case failure:
```
= FINISHED o.a.s.sql.jdbc.OracleIntegratio
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15192
**[Test build #71746 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71746/testReport)**
for PR 15192 at commit
[`d8cbe54`](https://github.com/apache/spark/commit/d8
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15192
Will also run the docker integration tests in my local computer. Post the
results later. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on G
Github user sureshthalamati commented on the issue:
https://github.com/apache/spark/pull/15192
@gatorsmile Verified on the master , problem still exist. Resolved the
conflicts, when u get a chance can you please review.
Error stack without the fix
java.lang.NullPointerEx
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15192
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15192
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71648/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15192
**[Test build #71648 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71648/testReport)**
for PR 15192 at commit
[`eeba2b1`](https://github.com/apache/spark/commit/e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15192
**[Test build #71648 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71648/testReport)**
for PR 15192 at commit
[`eeba2b1`](https://github.com/apache/spark/commit/ee
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15192
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 feature
enabled and wishes so, or if the
Github user sureshthalamati commented on the issue:
https://github.com/apache/spark/pull/15192
sure. I will resolve the conflicts today.
---
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 thi
Github user gatorsmile commented on the issue:
https://github.com/apache/spark/pull/15192
The original support by array type is done in
https://github.com/apache/spark/pull/9662. Could you resolve the conflicts and
reproduce the error in the latest code base?
---
If your project is
Github user miketrewartha commented on the issue:
https://github.com/apache/spark/pull/15192
@sureshthalamati Any plans to get the conflicts fixed here and get things
merged?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user sureshthalamati commented on the issue:
https://github.com/apache/spark/pull/15192
@srowen SPARK-14536 is not a duplicate, this PR will address the issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15192
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65751/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15192
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
e
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15192
**[Test build #65751 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65751/consoleFull)**
for PR 15192 at commit
[`9eb40db`](https://github.com/apache/spark/commit/
Github user sureshthalamati commented on the issue:
https://github.com/apache/spark/pull/15192
@JoshRosen
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/15192
**[Test build #65751 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65751/consoleFull)**
for PR 15192 at commit
[`9eb40db`](https://github.com/apache/spark/commit/9
28 matches
Mail list logo
