[jira] [Commented] (KAFKA-3411) Streams: stop using "job" terminology, rename job.id to application.id

[ https://issues.apache.org/jira/browse/KAFKA-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197199#comment-15197199 ] ASF GitHub Bot commented on KAFKA-3411: --- GitHub user miguno opened a pull request:

[GitHub] kafka pull request: KAFKA-3411: Streams: stop using "job" terminol...

GitHub user miguno opened a pull request: https://github.com/apache/kafka/pull/1081 KAFKA-3411: Streams: stop using "job" terminology, rename job.id to application.id @guozhangwang @ymatsuda : please review. You can merge this pull request into a Git repository by running: $ g

[jira] [Created] (KAFKA-3411) Streams: rename job.id to application.id

Michael Noll created KAFKA-3411: --- Summary: Streams: rename job.id to application.id Key: KAFKA-3411 URL: https://issues.apache.org/jira/browse/KAFKA-3411 Project: Kafka Issue Type: Improvement

[jira] [Updated] (KAFKA-3411) Streams: stop using "job" terminology, rename job.id to application.id

[ https://issues.apache.org/jira/browse/KAFKA-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Noll updated KAFKA-3411: Summary: Streams: stop using "job" terminology, rename job.id to application.id (was: Streams: rena

[jira] [Closed] (KAFKA-3401) Message format change on the fly breaks 0.9 consumer

[ https://issues.apache.org/jira/browse/KAFKA-3401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eno Thereska closed KAFKA-3401. --- > Message format change on the fly breaks 0.9 consumer > -

Re: [DISCUSS] KIP-35 - Retrieve protocol version

1. But there is no way of conveying version mismatch in the protocol, that's one of the reasons for this KIP in the first place :) Even if there was (e.g., the empty response hack) it makes the client implementation more complex since the cached cluster-level version support returned by the broker