[
https://issues.apache.org/jira/browse/SPARK-12177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335311#comment-15335311
]
Cody Koeninger commented on SPARK-12177:
----------------------------------------
[~jinx...@ebay.com] Replied by email, but just to put this in the right place
in the thread - yes, it's related to that ticket.
To be clear, you don't need to modify DirectKafkaInputDStream to work around
this. In the DriverConsumer, you can do whatever setup you need, including
seeking to a particular position. There's an example of this here:
https://github.com/koeninger/kafka-exactly-once/blob/kafka-0.9/src/main/scala/example/TransactionalExample.scala#L67
That's one example of why I think trying to hide the consumer is a bad idea.
> Update KafkaDStreams to new Kafka 0.10 Consumer API
> ---------------------------------------------------
>
> Key: SPARK-12177
> URL: https://issues.apache.org/jira/browse/SPARK-12177
> Project: Spark
> Issue Type: Improvement
> Components: Streaming
> Affects Versions: 1.6.0
> Reporter: Nikita Tarasenko
> Labels: consumer, kafka
>
> Kafka 0.9 already released and it introduce new consumer API that not
> compatible with old one. So, I added new consumer api. I made separate
> classes in package org.apache.spark.streaming.kafka.v09 with changed API. I
> didn't remove old classes for more backward compatibility. User will not need
> to change his old spark applications when he uprgade to new Spark version.
> Please rewiew my changes
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
