Github user yucai commented on the issue:
https://github.com/apache/spark/pull/19788
Currently users need update their external shuffle service for this
feature, because we change the format of `ShuffleBlockId`, which is supposed to
be parsed by external shuffle service.
I am trying to introduce a new configure like
`spark.shuffle.continuousFetch`. By default, it is `false`, Spark will still
use `ShuffleBlockId` as always, and when it is set `true` intentionally, Spark
will use `ContinuousShuffleBlockIds`. In this way, users no need update their
external shuffle service if they only want to work with `ShuffleBlockId`.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
