Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/6672#issuecomment-114884294
For the HistoryServer, it would only really be the final aggregated state
that we care about, except the problem is that the event log would store the
entire event stream used to construct that state, which could be huge. There
might be hacks / tricks that we could come up with to persist the aggregated
block info but we might want to consider them separately as part of a larger
discussion of HistoryServer designs for long-running applications.
---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
