[
https://issues.apache.org/jira/browse/FLINK-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679786#comment-14679786
]
ASF GitHub Bot commented on FLINK-2386:
---------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/996#issuecomment-129363319
Thanks for all the information Robert! I will have a more detailed look at
the classes you mentioned until you are back. Regarding the open questions:
1) Copying code
- I don't see a problem with this in general. I would assume that the
copied solution will lead to less surprises in the end. After the new API is
released by Kafka, we can remove the code, right?
2) Packaging
- I think it's OK with proper documentation and as you said we have to do
it anyways at some point in time.
---
I've started a discussion about a bug fix release for 0.9. I think this
issue is a blocker for that release. What's your stand on this? What do you
think how much longer it will take after you are back?
> Implement Kafka connector using the new Kafka Consumer API
> ----------------------------------------------------------
>
> Key: FLINK-2386
> URL: https://issues.apache.org/jira/browse/FLINK-2386
> Project: Flink
> Issue Type: Improvement
> Components: Kafka Connector
> Reporter: Robert Metzger
> Assignee: Robert Metzger
>
> Once Kafka has released its new consumer API, we should provide a connector
> for that version.
> The release will probably be called 0.9 or 0.8.3.
> The connector will be mostly compatible with Kafka 0.8.2.x, except for
> committing offsets to the broker (the new connector expects a coordinator to
> be available on Kafka). To work around that, we can provide a configuration
> option to commit offsets to zookeeper (managed by flink code).
> For 0.9/0.8.3 it will be fully compatible.
> It will not be compatible with 0.8.1 because of mismatching Kafka messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
