Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/325
---
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 enabl
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40114453
Okay thanks, merged!
---
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 fe
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40114262
@AndreSchumacher it's likely related to an accidental merge of a buggy
patch into master... try rebasing to the latest master which includes a
reversion of the bug.
---
Github user AndreSchumacher commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40072003
I'm seeing some Akka related problems in my local build but nothing that
would seem related to this PR. The log forwarding seems to work.
@pwendell thanks
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40062916
Merged build finished. All automated tests 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40062919
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13998/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40060072
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40060060
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40059900
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13996/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40059898
Merged build finished.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40059933
Jenkins, test 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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40055296
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40055287
Merged build triggered.
---
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 ha
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40055267
Jenkins, test 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 t
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40054373
no we don't need to change the dependencies. The case I wanted to handle
was if users downstream remove the dependencies (e.g. they remove
"jul-to-slf4j") and do a custom
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40052128
@pwendell
Thank you, this patch works
But this only solve one problem. The Spark the dependence of the is fixed,
we can only use log4j.
In SparkBuild.s
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40050637
@witgo I gave an example of using reflection - mind adjusting your patch
and checking if this works?
---
If your project is set up for it, you can reply to this email an
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11473388
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11472274
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var in
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11472039
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11471966
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var in
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11471958
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var i
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11471909
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11471870
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11471838
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11471046
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var i
Github user witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11467386
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var in
Github user julienledem commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40033694
@pwendell I'm perfectly happy with removing this static initialization in
parquet:
https://github.com/Parquet/parquet-mr/blob/41df19051825d724626e91425c8e690c04a39
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11465928
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/325#discussion_r11465350
--- Diff: core/src/main/scala/org/apache/spark/Logging.scala ---
@@ -135,4 +136,6 @@ trait Logging {
private object Logging {
@volatile private var
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-40030692
It is probably another flakey streaming test. Lets try again...
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39950391
Strange, I run the test is pass.
`mvn -Dhadoop.version=0.23.9 -Dyarn.version=0.23.9 -Pyarn-alpha test
-Dsuites=org.apache.spark.streaming.flume.FlumeStreamSuite`
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39940056
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13941/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39940055
Merged build finished.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39936420
Merged build started.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39936414
Merged build triggered.
---
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 ha
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39936344
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39935838
Merged build finished.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39935839
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13938/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39933461
Merged build triggered.
---
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39933469
Merged build started.
---
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 AndreSchumacher commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39933315
Jenkins, test 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
Github user AndreSchumacher commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39863563
OK, looks good to me. I just tried and changing the Log4J config has the
desired effect and the console does not lock up. I can't explain why the CI
test is failin
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39819593
@AndreSchumacher
You're right,the code has been modified.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/325#issuecomment-39545021
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 proj
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/325
Fix SPARK-1413: Parquet messes up stdout and stdin when used in Spark REPL
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-1413
46 matches
Mail list logo
