Github user advancedxy commented on the issue:
https://github.com/apache/spark/pull/21445
> I think the best way to do it is to make the shuffle writer responsible
for incrementing the epoch within its task, the same way the data source writer
does currently.
Yeah, @LiangchangZ please consider this way. The writer part of a task is
responsible to pull data from upstream. It's more consistent and wouldn't break
existing logic.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
