[ https://issues.apache.org/jira/browse/SPARK-15406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15453789#comment-15453789 ]
Cody Koeninger edited comment on SPARK-15406 at 9/1/16 2:26 AM: ---------------------------------------------------------------- There's a big difference between continuing to publish an existing implementation that requires little to no maintenance, and putting new development work into a dead version. I don't think removing existing functionality for Kafka 0.8 users makes sense. Nor do I think new development should be chained to old versions. We already had this argument around the Kafka connector, and I believe it was resolved in a sensible way - keep the old existing code around, but stop putting effort into it. was (Author: c...@koeninger.org): There's a big difference between continuing to publish an existing implementation that is requires little to no maintenance, and putting new development work into a dead version. I don't think removing existing functionality for Kafka 0.8 users makes sense. Nor do I think new development should be chained to old versions. We already had this argument around the Kafka connector, and I believe it was resolved in a sensible way - keep the old existing code around, but stop putting effort into it. On Aug 31, 2016 18:45, "Frederick Reiss (JIRA)" <j...@apache.org> wrote: [ https://issues.apache.org/jira/browse/SPARK-15406?page= com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel&focusedCommentId=15453749#comment-15453749 ] Frederick Reiss commented on SPARK-15406: ----------------------------------------- WRT Kafka 0.8: I'm under the impression that there is a significant number of Spark users who are still stuck with Kafka 0.8 or 0.9. Kafka sits between multiple systems, so upgrades to production Kafka installations can be challenging. Are other people monitoring this JIRA seeing a similar situation, or are versions before 0.10 not in widespread use any more? If older Kafka releases aren't relevant, then we should probably deprecate the entire spark-streaming-kafka-0-8 component. feel like time based indexing would make for a much better interface, but it's been pushed back to kafka 0.10.1 33+-+Add+a+time+based+log+index -- This message was sent by Atlassian JIRA (v6.3.4#6332) > Structured streaming support for consuming from Kafka > ----------------------------------------------------- > > Key: SPARK-15406 > URL: https://issues.apache.org/jira/browse/SPARK-15406 > Project: Spark > Issue Type: New Feature > Reporter: Cody Koeninger > > Structured streaming doesn't have support for kafka yet. I personally feel > like time based indexing would make for a much better interface, but it's > been pushed back to kafka 0.10.1 > https://cwiki.apache.org/confluence/display/KAFKA/KIP-33+-+Add+a+time+based+log+index -- 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