[
https://issues.apache.org/jira/browse/SPARK-12177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15203018#comment-15203018
]
Eugene Miretsky commented on SPARK-12177:
-----------------------------------------
The new Kafka Java Consumer is using Deserializer<T> instead of Decoder. The
difference is not too big (extra type safety, and Deserializer::deserialize
accepts a topic and a byte payload, while Decoder::fromBytes accepts only a
byte payload), but still it would be nice to align with the new Kafka consumer.
Would it make sense to replace Decoder with Deserializer<T> in the new
DirectStream? This would require getting rid of MessageAndMetadata, and hence
breaking backwards compatibility with the existing DirectStream, but I guess
it will have to be done at some point.
> 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
