Github user hejix commented on the issue:
https://github.com/apache/spark/pull/17012
@zsxwing Is it possible for you to give some approximate timeframe for when
this might be accepted? A week or month? Since we are blocked in our spark
streaming adoption (this HDFS error happens not only in restart but also in
first run of our more complex aggregating drivers), I don't know if I should
wait for this fix to make it into the nightly build soon or build a custom dist
ourselves and update our automation. Any input as to the fix timeline would be
greatly appreciated!
Also this fix handles the same issue as SPARK-19645 which has a different
solution. Is this simple solution sufficient or the more complex fix in
https://github.com/apache/spark/pull/16980 required?
---
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
