Github user koeninger commented on a diff in the pull request:
https://github.com/apache/spark/pull/15504#discussion_r84371466
--- Diff:
external/kafka-0-10-sql/src/main/scala/org/apache/spark/sql/kafka010/KafkaSource.scala
---
@@ -317,6 +353,8 @@ private[kafka010] case class KafkaSource(
try {
result = Some(body)
} catch {
+ case x: OffsetOutOfRangeException =>
--- End diff --
OffsetOutOfRange exeception can happen on any poll. I agree that with the
way things are now, it shouldn't happen, but that has more to do with us
currently having an explictly enforced value for auto.offset.reset, not with
whether data is being fetched. This change is basically paranoia about catching
all nonfatal errors without respecting user settings regarding data loss.
---
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
