Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/22353
thanks, merging to master/2.4/2.3!
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands,
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22353
Merged build finished. Test PASSed.
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/22353
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95993/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/22353
**[Test build #95993 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/95993/testReport)**
for PR 22353 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/22353
**[Test build #95993 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/95993/testReport)**
for PR 22353 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/22353
ok to test
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail:
Github user LantaoJin commented on the issue:
https://github.com/apache/spark/pull/22353
ping @cloud-fan
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail:
Github user LantaoJin commented on the issue:
https://github.com/apache/spark/pull/22353
Thank you @cloud-fan for your reminding. Weâve handled the drop message
case. Agree, I will update a commit tomorrow.
---
-
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/22353
So you need a way to reliably report some extra information like file path
in the event logs, but don't want to show it in the UI as it maybe too long.
Basically we shouldn't put such
Github user LantaoJin commented on the issue:
https://github.com/apache/spark/pull/22353
Spark driver log is always distributed on various client nodes and depends
on the log4j configs. In a big company, it's hard to collect them all and I
think it's better to used for debug not
Github user LantaoJin commented on the issue:
https://github.com/apache/spark/pull/22353
> Although event log is in JSON format, it's mostly for internal usage, to
be load by history server and used to build the Spark UI.
AFAIK, there are more and more projects replay event log to
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/22353
Although event log is in JSON format, it's mostly for internal usage, to be
load by history server and used to build the Spark UI. For compatibility, we
only focus on making history to be able to
12 matches
Mail list logo
