[
https://issues.apache.org/jira/browse/KAFKA-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guozhang Wang resolved KAFKA-3411.
----------------------------------
Resolution: Fixed
Fix Version/s: 0.10.0.0
Issue resolved by pull request 1081
[https://github.com/apache/kafka/pull/1081]
> Streams: stop using "job" terminology, rename job.id to application.id
> ----------------------------------------------------------------------
>
> Key: KAFKA-3411
> URL: https://issues.apache.org/jira/browse/KAFKA-3411
> Project: Kafka
> Issue Type: Improvement
> Components: kafka streams
> Affects Versions: 0.10.0.0
> Reporter: Michael Noll
> Priority: Minor
> Fix For: 0.10.0.0
>
>
> Background: We stopped using the terminology of a "job" in the context of
> Kafka Streams. For example, the upcoming Streams docs do not refer to a
> "job" anymore; otherwise it's very confusing to readers that are familiar
> with "jobs" in Hadoop, Spark, Storm, etc. because there's no equivalent
> concept of a "job" in Streams.
> We should update the Streams code (see "cd streams/ ; git grep job" for a
> starting point) to reflect this accordingly. Notably, the configuration
> option "job.id" should be changed to "application.id".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
