[
https://issues.apache.org/jira/browse/SPARK-12177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177315#comment-15177315
]
Mark Grover commented on SPARK-12177:
-------------------------------------
One more thing as a potential con for Proposal 1:
There are places that have to use the kafka artifact. 'examples' subproject is
a good example of that. The subproject pulls kafka artifact as a dependency and
has example for Kafka usage. However, it can't depend on the new
implementation's artifact at the same time because they depend on different
versions of kafka. Therefore, unless I am missing something, new
implementation's example can't go there.
And, that's fine, we can put it within the subproject itself, instead of
examples, but that won't necessarily work with tooling like run-example, etc.
> 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
