Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/6864#issuecomment-113449649
@chenghao-intel Thanks for the comment! Speculation is a great point that I
didn't notice. Updated this PR and now use a job level UUID instead of a task
level one. Because essentially, what we want is to avoid name collision between
different write jobs (potentially issued by different Spark applications).
Within a single write job, we can always avoid name collision with the help of
task ID.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
