Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4548#issuecomment-74047686
The idea is that this uniquely determines the file and even a version of
that file. That by itself is sound. Timestamp is not always "the current time".
Look at the invocation in `Executor.scala`. I'm not as sure about the
invocation in `SparkContext.scala` since it also does a fetch locally, with the
current time, and that is always a 'cache miss', but I think that one is by
design? But for the executor it looks correct at first glance since it uses
timestamp as a sort of version key, where the timestamp is the time this
particular file was added by the driver.
---
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]
