Github user koeninger commented on the pull request:
https://github.com/apache/spark/pull/11143#issuecomment-190914907
I really don't think it makes sense to discuss this PR outside of the
context of SPARK-12177 and the approach taken for supporting the new consumer.
Merging it as is would break things for end users without giving them any new
features as a benefit, and nothing in Spark 2.0 that I'm aware of otherwise
requires the kafka version bump.
If SPARK-12177 ends up being implemented as a separate artifact, this PR
isn't even necessary. If it ends up being implemented in the same artifact and
breaking 0.8 compatibility, this PR is a small drop in the bucket compared to
the overall code change and could be handled at that time.
Regarding the semi-private apis, those are either in testing code, or in
the receiver-based implementation which (so far) no one has shown a lot of
interest in updating for the new consumer.
---
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
