Github user srowen commented on the issue:
https://github.com/apache/spark/pull/16527
Yes, I'm suggesting the behavior you describe isn't desirable. Right now,
if there are 150 items and max is 100, it will delete 50. That's good. There's
no good reason to delete 10 more than needed for performance. The problem case
is where there is just 101 and the max is 100. Then it makes sense to enforce a
minimum number removed.
I'm suggesting dropping `math.max((retainedSize * 0.1).toInt, dataSize -
retainedSize)` in each case.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
