Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20575
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user gerashegalov commented on the issue:
https://github.com/apache/spark/pull/20575
Thanks for suggestions, I will look into them. I agree that a solution into
the right direction will definitely involve changing the write call path. I did
not go down this path because I have
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/20575
True. Still, to be able to do that, you're hardcoding YARN-isms into the
code, e.g., how application IDs look, so that you can create a "fake"
application entry that will, hopefully, eventually
Github user gerashegalov commented on the issue:
https://github.com/apache/spark/pull/20575
@vanzin what do you mean by "as part of parsing the logs"? This PR is about
avoiding the long wait for eventLogs to be read from a remote filesystem, and
being parsed.
---
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/20575
If doing this, it would be cleaner to do it as part of parsing the logs.
e.g., if you make `AppListingListener` write the app info to the store when
interesting events happen, that would be much
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20575
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/20575
Can one of the admins verify this patch?
---
-
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional
