Github user steveloughran commented on the pull request:
https://github.com/apache/spark/pull/10648#issuecomment-171525569
I have some opinions too, as with YARN timeline service integration, it's
essentially hooked up to a database, both for publishing and retrieval. It
might be interesting to consider a dual mode, where things are published to
HDFS/s3/WASB during a run (availability will match that of the analytics work
itself), and for retrieval, after any initial load & parse, persist in a DB.
You could do that with the current FS records, extracting useful summary data
"completed" "incompatible-version" in the process.
---
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]
