Github user koeninger commented on the issue:
https://github.com/apache/spark/pull/15407
This doesn't affect correctness (only the highest offset for a given
partition is used in any case), just memory leaks. I'm not sure what a good
way to unit test memory leaks is, short of exposing the internal state of that
queue, which seems less than optimal.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
