Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16573
Since the log level is not stored in Spark, we cannot recover the correct
level if the user just uses
`org.apache.log4j.Logger.getRootLogger().setLevel(l)` to set. In addition, if I
use
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16573
@zsxwing I know what you mean, and indeed it can achieve the right result!
IMHO, since we have provided the `SparkContext.setLogLevel`, it is weird to
call
Github user zsxwing commented on the issue:
https://github.com/apache/spark/pull/16573
You can just call `org.apache.log4j.Logger.getRootLogger().setLevel(l)` in
your main method before `StreamingContext.getOrCreate`. I don't think it's a
good idea to add a new Spark conf just for
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16573
also cc @tdas
---
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
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16573
@zsxwing Could you review this PR?
---
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 issue:
https://github.com/apache/spark/pull/16573
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16573
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71392/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16573
**[Test build #71392 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71392/testReport)**
for PR 16573 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16573
**[Test build #71392 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71392/testReport)**
for PR 16573 at commit
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/16573
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 this feature
enabled and wishes
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16573
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16573
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/71317/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16573
**[Test build #71317 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71317/testReport)**
for PR 16573 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16573
**[Test build #71317 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/71317/testReport)**
for PR 16573 at commit
14 matches
Mail list logo
