You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by GitBox <gi...@apache.org> on 2019/03/29 01:58:11 UTC
[GitHub] [spark] srowen commented on issue #24212:
[SPARK-26771][SQL][FOLLOWUP] Make all the uncache operations non-blocking
by default
srowen commented on issue #24212: [SPARK-26771][SQL][FOLLOWUP] Make all the uncache operations non-blocking by default
URL: https://github.com/apache/spark/pull/24212#issuecomment-477836078
Users can still control the blocking behavior for the Dataset/RDD/Broadcast objects, so I don't think it's worth a new config to change the default. I am also not sure if there's a reasonable scenario where someone needs the internal cache unpersist to be blocking? if memory pressure is an issue, lots of other things are more important than this. I would rather not add yet another random config for this.
----------------------------------------------------------------
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 comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org