HyukjinKwon closed pull request #43823: [SPARK-45942][CORE] Only do the thread
interruption check for putIterator on executors
URL: https://github.com/apache/spark/pull/43823
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
HyukjinKwon commented on PR #43823:
URL: https://github.com/apache/spark/pull/43823#issuecomment-1818148281
Merged to master.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
huanliwang-db commented on PR #43823:
URL: https://github.com/apache/spark/pull/43823#issuecomment-1816743997
looks like `RocksDBStateStoreStreamingAggregationSuite` fails consistently
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
HeartSaVioR commented on PR #43823:
URL: https://github.com/apache/spark/pull/43823#issuecomment-1815683617
Looks like one failure from SS is more likely a known flaky test. I have no
context on the failure in extended tests. @huanliwang-db could we please
retrigger CI via pushing an empty
mridulm commented on PR #43823:
URL: https://github.com/apache/spark/pull/43823#issuecomment-1815675753
Please check the sql slow tests failure ... I am not very familiar with it
to judge if it is related to this change.
Thoughts @HeartSaVioR ?
--
This is an automated message from the
huanliwang-db opened a new pull request, #43823:
URL: https://github.com/apache/spark/pull/43823
### What changes were proposed in this pull request?
Only do the thread interruption check for putIterator on executors
### Why are the changes needed?
