Nope, but when we migrated to spark 1.6, we didnt see the errors yet. Not sure if they fixed in between releases or it just be a weird timing thing that we havent discovered yet in 1.6 as well.
On Sat, Mar 4, 2017 at 12:00 AM, nimmi.cv [via Apache Spark User List] < ml-node+s1001560n28454...@n3.nabble.com> wrote: > Did you find out how ? > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > http://apache-spark-user-list.1001560.n3.nabble.com/How-to- > gracefully-handle-Kafka-OffsetOutOfRangeException-tp26534p28454.html > To unsubscribe from How to gracefully handle Kafka > OffsetOutOfRangeException, click here > <http://apache-spark-user-list.1001560.n3.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=26534&code=cmFtLnRoZS5tb25rQGdtYWlsLmNvbXwyNjUzNHwtNzE2NDQ4OTI5> > . > NAML > <http://apache-spark-user-list.1001560.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/How-to-gracefully-handle-Kafka-OffsetOutOfRangeException-tp26534p28479.html Sent from the Apache Spark User List mailing list archive at Nabble.com.
