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

2016-03-19 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/KAFKA-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15200014#comment-15200014
 ] 

ASF GitHub Bot commented on KAFKA-3411:
---

Github user asfgit closed the pull request at:

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)


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

2016-03-16 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/KAFKA-3411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197199#comment-15197199
 ] 

ASF GitHub Bot commented on KAFKA-3411:
---

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:

$ git pull https://github.com/miguno/kafka KAFKA-3411

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/kafka/pull/1081.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1081


commit 6bb7be2dc02fc8c3c6afabce05c1e8bac2426449
Author: Michael G. Noll 
Date:   2016-03-16T11:15:08Z

KAFKA-3411: Streams: stop using "job" terminology, rename job.id to 
application.id




> 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
>
> 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)