Github user koeninger commented on the pull request:
https://github.com/apache/spark/pull/11143#issuecomment-189365359
Kafka isn't just a library dependency that a user can try out a new version
of on a particular job and see if it works.
It's an infrastructure component that the entire business may depend on.
Upgrading running brokers is not risk-free.
From a user point of view, I think it's better to have an artifact that
works with spark 2.0 and kafka 0.8 brokers, even if that means moving the
existing code to a spark-streaming-kafka08 subproject and doing new development
on spark-streaming-kafka for kafka 0.9 (or, for that matter, kafka 0.10, which
may be out by the time Spark 2.0 is ready)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
