Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12192
---
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/12192#issuecomment-207369220
Merged 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
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-207175670
Please please merge it as soon as possible as I'm suffering from not having
it in master every time I do the build :(
---
If your project is set up for it, you
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-207107119
Sure. I agree for merging.
The underlying problem will be investigated and resolved someday.
---
If your project is set up for it, you can reply to this
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-207100250
I agree it's a bit of a strange problem. @dongjoon-hyun do you agree that
this change is worth merging? it seems like it fixes the immediate symptom of a
problem, even
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-207031919
Just for a record, here is the current error message from **doc-jar**. (The
version of doc-jar is the latest.)
```
[INFO] <<<
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-207025582
Hi, All.
The original code is made by me, so I feel guilty. :)
I think Jenkins build does not show additional information for this PR
since our
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206794165
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206794170
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/12192#issuecomment-206793924
**[Test build #55207 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55207/consoleFull)**
for PR 12192 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206760564
**[Test build #55207 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55207/consoleFull)**
for PR 12192 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206759561
Jenkins 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
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206098980
Hi, @jaceklaskowski and @marmbrus .
Thank you for fixing this. I didn't notice there is such a problem.
Sorry for late response!
I have another PR
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206095830
@tdas another streaming failure
---
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 jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206095697
Is this really the patch to cause the issue or is this more an interim
hiccup?
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206095409
Test FAILed.
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/12192#issuecomment-206095407
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206095328
**[Test build #55069 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55069/consoleFull)**
for PR 12192 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206069179
**[Test build #55069 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55069/consoleFull)**
for PR 12192 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206068825
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12192#issuecomment-206067810
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
GitHub user jaceklaskowski opened a pull request:
https://github.com/apache/spark/pull/12192
[HOTFIX][SPARK-14402] Fix ExpressionDescription annotation
## What changes were proposed in this pull request?
Fix for the error introduced in
22 matches
Mail list logo
