SuccessChanges

Summary

  1. [SPARK-24987][SS] - Fix Kafka consumer leak when no new offsets for (details)
Commit 14b50d7fee58d56cb8843994b1a423a6b475dcb5 by cody
[SPARK-24987][SS] - Fix Kafka consumer leak when no new offsets for
TopicPartition
## What changes were proposed in this pull request?
This small fix adds a `consumer.release()` call to `KafkaSourceRDD` in
the case where we've retrieved offsets from Kafka, but the `fromOffset`
is equal to the `lastOffset`, meaning there is no new data to read for a
particular topic partition. Up until now, we'd just return an empty
iterator without closing the consumer which would cause a FD leak.
If accepted, this pull request should be merged into master as well.
## How was this patch tested?
Haven't ran any specific tests, would love help on how to test methods
running inside `RDD.compute`.
Author: Yuval Itzchakov <yuval.itzchakov@clicktale.com>
Closes #21997 from YuvalItzchakov/master.
(cherry picked from commit b7fdf8eb2011ae76f0161caa9da91e29f52f05e4)
Signed-off-by: cody koeninger <cody@koeninger.org>
The file was modifiedexternal/kafka-0-10-sql/src/main/scala/org/apache/spark/sql/kafka010/KafkaSourceRDD.scala (diff)