[ 
https://issues.apache.org/jira/browse/SPARK-12177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203662#comment-15203662
 ] 

Eugene Miretsky commented on SPARK-12177:
-----------------------------------------

1) MessageAndMetaData: Was looking at KafkaRDD instead of NewKafkaRDD by 
mistake - my bad. 

2)Decoder/Serializer: DirectKafkaInputDStreamBase has U <: Decoder[K]: 
ClassTag,  T <: Decoder[V]: ClassTag type parameters.
-  NewDirectKafkaInputDStream ignores the Decoder TypeTags. (The old 
DirectKafkaInputDStream passes them to KafkaRDDIterator which then creates 
valueDecoder & keyDecoder which are then passed to MessageAndMetaData). 
- kafka.serializer.Decoder in part of the old Scala Kafka Consumer, The new 
Kafka Java Consumer is using 
org.apache.kafka.common.serialization.Deserializer. 

Just to make sure we are on the same page - I'm looking at PR 10953. Also may 
have missed something. 

> Update KafkaDStreams to new Kafka 0.9 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

Reply via email to