Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/22894
Practically, though, it generates a whole copy of the map at every update,
so for 10 items, the implementation in the PR generates 9 copies of 1, 2, 3,
... elements, while the current one generates only 1 copy, at the end of size
10. So the proposed change is worse than the current solution. If you create a
benchmark, you can see this.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
