Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-206611258
Hi, @rxin .
I made a new PR for ScalaStyle rule enforcement ( #12221 ).
---
If your project is set up for it, you can reply to this email and have your
reply
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204898177
Thank you, @rxin . I see. I'll create a JIRA for large size patch .
And, for creating new ScalaStyle rule to enforce this seems a good idea.
I'll take a loo
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12130
---
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 ena
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204838383
BTW in the future for changes this size we should create a JIRA ticket.
Can you look into whether it is possible to create a scalastyle rule for
this so we don't d
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204838369
Thanks - merging in 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204814623
**[Test build #2734 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2734/consoleFull)**
for PR 12130 at commit
[`51ab3ba`](https://
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204802236
**[Test build #2734 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2734/consoleFull)**
for PR 12130 at commit
[`51ab3ba`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204793312
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204793307
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204793067
**[Test build #54779 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54779/consoleFull)**
for PR 12130 at commit
[`51ab3ba`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204769169
**[Test build #54779 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54779/consoleFull)**
for PR 12130 at commit
[`51ab3ba`](https://gi
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204769078
Rebased to trigger Jenkins 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 d
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204767494
`org.apache.spark.sql.execution.streaming.state.StateStoreSuite.maintenance`
failure again.
It's a timeout error, should we increase the timeout for the test
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204700424
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204700422
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204700391
**[Test build #54770 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54770/consoleFull)**
for PR 12130 at commit
[`9c06d60`](https://g
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204688228
Could you review this PR, @rxin ?
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12130#issuecomment-204685184
**[Test build #54770 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54770/consoleFull)**
for PR 12130 at commit
[`9c06d60`](https://gi
GitHub user dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/12130
[MINOR][DOCS] Use multi-line JavaDoc comments in Scala code.
## What changes were proposed in this pull request?
This PR aims to fix all Scala-Style multiline comments into Java-Style
19 matches
Mail list logo
