[jira] [Updated] (FLINK-4723) Unify behaviour of committed offsets to Kafka / ZK for Kafka 0.8 and 0.9 consumer

2016-10-01 Thread Tzu-Li (Gordon) Tai (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tzu-Li (Gordon) Tai updated FLINK-4723: --- Summary: Unify behaviour of committed offsets to Kafka / ZK for Kafka 0.8 and 0.9

[jira] [Updated] (FLINK-4723) Unify behaviour of committed offsets to Kafka / ZK for Kafka 0.8 and 0.9 consumer

2016-10-01 Thread Tzu-Li (Gordon) Tai (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tzu-Li (Gordon) Tai updated FLINK-4723: --- Description: The proper "behaviour" of the offsets committed back to Kafka / ZK

[jira] [Commented] (FLINK-4724) When executed in YARN wrong log4j & logback configuration file are used

2016-10-01 Thread Eron Wright (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15539453#comment-15539453 ] Eron Wright commented on FLINK-4724: - The log4j-yarn-session.properties file is used by the

[jira] [Created] (FLINK-4725) BucketingSink throws NPE while restoring state if basePath does not exist

2016-10-01 Thread Jordan Ganoff (JIRA)
Jordan Ganoff created FLINK-4725: Summary: BucketingSink throws NPE while restoring state if basePath does not exist Key: FLINK-4725 URL: https://issues.apache.org/jira/browse/FLINK-4725 Project:

[jira] [Created] (FLINK-4724) When executed in YARN wrong log4j & logback configuration file is used

2016-10-01 Thread Melmoth (JIRA)
Melmoth created FLINK-4724: -- Summary: When executed in YARN wrong log4j & logback configuration file is used Key: FLINK-4724 URL: https://issues.apache.org/jira/browse/FLINK-4724 Project: Flink

[jira] [Updated] (FLINK-4724) When executed in YARN wrong log4j & logback configuration file are used

2016-10-01 Thread Melmoth (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Melmoth updated FLINK-4724: --- Summary: When executed in YARN wrong log4j & logback configuration file are used (was: When executed in YARN

[jira] [Updated] (FLINK-4723) Unify definition of committed offsets to Kafka / ZK for Kafka 0.8 and 0.9 consumer

2016-10-01 Thread Tzu-Li (Gordon) Tai (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tzu-Li (Gordon) Tai updated FLINK-4723: --- Description: The proper "definition" of the offsets committed back to Kafka / ZK

[jira] [Updated] (FLINK-4723) Unify definition of committed offsets to Kafka / ZK for Kafka 0.8 and 0.9 consumer

2016-10-01 Thread Tzu-Li (Gordon) Tai (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tzu-Li (Gordon) Tai updated FLINK-4723: --- Description: The proper "definition" of the offsets committed back to Kafka / ZK

[jira] [Updated] (FLINK-4723) Unify definition of committed offsets to Kafka / ZK for Kafka 0.8 and 0.9 consumer

2016-10-01 Thread Tzu-Li (Gordon) Tai (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tzu-Li (Gordon) Tai updated FLINK-4723: --- Description: The proper "definition" of the offsets committed back to Kafka / ZK

[jira] [Created] (FLINK-4723) Unify definition of committed offsets to Kafka / ZK for Kafka 0.8 and 0.9 consumer

2016-10-01 Thread Tzu-Li (Gordon) Tai (JIRA)
Tzu-Li (Gordon) Tai created FLINK-4723: -- Summary: Unify definition of committed offsets to Kafka / ZK for Kafka 0.8 and 0.9 consumer Key: FLINK-4723 URL: https://issues.apache.org/jira/browse/FLINK-4723

[jira] [Resolved] (FLINK-4618) FlinkKafkaConsumer09 should start from the next record on startup from offsets in Kafka

2016-10-01 Thread Tzu-Li (Gordon) Tai (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tzu-Li (Gordon) Tai resolved FLINK-4618. Resolution: Fixed > FlinkKafkaConsumer09 should start from the next record on

[jira] [Commented] (FLINK-4618) FlinkKafkaConsumer09 should start from the next record on startup from offsets in Kafka

2016-10-01 Thread Tzu-Li (Gordon) Tai (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15538306#comment-15538306 ] Tzu-Li (Gordon) Tai commented on FLINK-4618: Resolved for master via

[GitHub] flink pull request #2579: [FLINK-4618] FlinkKafkaConsumer09 should start fro...

2016-10-01 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/2579 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (FLINK-4618) FlinkKafkaConsumer09 should start from the next record on startup from offsets in Kafka

2016-10-01 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15538292#comment-15538292 ] ASF GitHub Bot commented on FLINK-4618: --- Github user asfgit closed the pull request at:

[jira] [Commented] (FLINK-4618) FlinkKafkaConsumer09 should start from the next record on startup from offsets in Kafka

2016-10-01 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15538287#comment-15538287 ] ASF GitHub Bot commented on FLINK-4618: --- Github user tzulitai commented on the issue:

[GitHub] flink issue #2579: [FLINK-4618] FlinkKafkaConsumer09 should start from the n...

2016-10-01 Thread tzulitai
Github user tzulitai commented on the issue: https://github.com/apache/flink/pull/2579 Merging ... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if

[jira] [Created] (FLINK-4722) Consumer group concept not working properly with FlinkKafkaConsumer09

2016-10-01 Thread Sudhanshu Sekhar Lenka (JIRA)
Sudhanshu Sekhar Lenka created FLINK-4722: - Summary: Consumer group concept not working properly with FlinkKafkaConsumer09 Key: FLINK-4722 URL: https://issues.apache.org/jira/browse/FLINK-4722

[jira] [Commented] (FLINK-4348) Implement slot allocation protocol with TaskExecutor

2016-10-01 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-4348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15538049#comment-15538049 ] ASF GitHub Bot commented on FLINK-4348: --- Github user KurtYoung commented on the issue:

[GitHub] flink issue #2571: [FLINK-4348] Simplify logic of SlotManager

2016-10-01 Thread KurtYoung
Github user KurtYoung commented on the issue: https://github.com/apache/flink/pull/2571 @mxm Regarding the last heartbeat thing, what i really trying to say is, the failing free request will not stuck in the unconfirmed list forever, since we have the heartbeat manager to monitoring