Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-73622237
Thanks! Merging to master and 1.3
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2405
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-73356972
[Test build #26994 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26994/consoleFull)
for PR 2405 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-73356946
Hi @marmbrus , since https://github.com/apache/spark/pull/4068 is merged,
it's much simpler to implement this now. Do you have time to review it? Thanks!
---
If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-73358865
[Test build #26994 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26994/consoleFull)
for PR 2405 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-73358866
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-69475869
/cc @rxin
Another API question.
---
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/2405#issuecomment-68096991
[Test build #24819 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24819/consoleFull)
for PR 2405 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-68099780
[Test build #24819 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24819/consoleFull)
for PR 2405 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-68099783
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user ayoub-benali commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-67317575
Hi @marmbrus @liancheng will this PR be part of the 1.2.0 branch ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-67375207
Its not ready to be merged yet, and 1.2.0 has already been finalized. I
think it would be great to revisit the implementation once #3724 goes in
(hopefully today). I
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-67432312
Hi, @marmbrus ,the key point why I want to introduce `UnResolvedGetField`
is that: for something like `a.b[0].c.d`, we first parse it to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-66592619
[Test build #24360 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24360/consoleFull)
for PR 2405 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-66592751
[Test build #24360 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24360/consoleFull)
for PR 2405 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-66592755
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-66593009
Hi @marmbrus @liancheng, I have updated this PR to support `GetField` on
one level of array of struct for now. As I mentioned in
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-66593677
[Test build #24362 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24362/consoleFull)
for PR 2405 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-66594023
[Test build #24362 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24362/consoleFull)
for PR 2405 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-66594025
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-66604421
[Test build #24363 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24363/consoleFull)
for PR 2405 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-66611502
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2405#issuecomment-66611497
[Test build #24363 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/24363/consoleFull)
for PR 2405 at commit
23 matches
Mail list logo
