[jira] [Comment Edited] (KAFKA-5440) Kafka Streams report state RUNNING even if all threads are dead

[ https://issues.apache.org/jira/browse/KAFKA-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127637#comment-16127637 ] Tommy Becker edited comment on KAFKA-5440 at 8/15/17 5:56 PM: -- To answer my

[jira] [Commented] (KAFKA-5440) Kafka Streams report state RUNNING even if all threads are dead

[ https://issues.apache.org/jira/browse/KAFKA-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127637#comment-16127637 ] Tommy Becker commented on KAFKA-5440: - To answer my own question, from what I can tell the PR for

[jira] [Commented] (KAFKA-5440) Kafka Streams report state RUNNING even if all threads are dead

[ https://issues.apache.org/jira/browse/KAFKA-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127316#comment-16127316 ] Tommy Becker commented on KAFKA-5440: - Any update on this? We're seeing the same behavior and I though

[jira] [Comment Edited] (KAFKA-5440) Kafka Streams report state RUNNING even if all threads are dead

[ https://issues.apache.org/jira/browse/KAFKA-5440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16127316#comment-16127316 ] Tommy Becker edited comment on KAFKA-5440 at 8/15/17 2:41 PM: -- Any update on

[jira] [Created] (KAFKA-6069) Streams metrics tagged incorrectly

Tommy Becker created KAFKA-6069: --- Summary: Streams metrics tagged incorrectly Key: KAFKA-6069 URL: https://issues.apache.org/jira/browse/KAFKA-6069 Project: Kafka Issue Type: Bug

[jira] [Commented] (KAFKA-5886) Introduce delivery.timeout.ms producer config (KIP-91)

[ https://issues.apache.org/jira/browse/KAFKA-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187976#comment-16187976 ] Tommy Becker commented on KAFKA-5886: - Thanks for the response. Though the KIP may be an improvement,

[jira] [Commented] (KAFKA-5886) Introduce delivery.timeout.ms producer config (KIP-91)

[ https://issues.apache.org/jira/browse/KAFKA-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16188552#comment-16188552 ] Tommy Becker commented on KAFKA-5886: - [~sutambe] yes that sounds great which is why I was hoping this

[jira] [Comment Edited] (KAFKA-5886) Introduce delivery.timeout.ms producer config (KIP-91)

[ https://issues.apache.org/jira/browse/KAFKA-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16186303#comment-16186303 ] Tommy Becker edited comment on KAFKA-5886 at 9/29/17 7:51 PM: -- Is this still

[jira] [Commented] (KAFKA-5886) Introduce delivery.timeout.ms producer config (KIP-91)

[ https://issues.apache.org/jira/browse/KAFKA-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16186303#comment-16186303 ] Tommy Becker commented on KAFKA-5886: - Is this still on track for 1.0? We just hit an issue with

[jira] [Commented] (KAFKA-6259) Make KafkaStreams.cleanup() clean global state directory

[ https://issues.apache.org/jira/browse/KAFKA-6259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16262987#comment-16262987 ] Tommy Becker commented on KAFKA-6259: - I literally just noticed this yesterday, and was wondering if

[jira] [Commented] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534259#comment-16534259 ] Tommy Becker commented on KAFKA-4113: - Coming from Samza, I find it very surprising that there is no

[jira] [Comment Edited] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534259#comment-16534259 ] Tommy Becker edited comment on KAFKA-4113 at 7/5/18 11:09 PM: -- Coming from

[jira] [Comment Edited] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534259#comment-16534259 ] Tommy Becker edited comment on KAFKA-4113 at 7/5/18 11:04 PM: -- Coming from

[jira] [Commented] (KAFKA-4113) Allow KTable bootstrap

[ https://issues.apache.org/jira/browse/KAFKA-4113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16535220#comment-16535220 ] Tommy Becker commented on KAFKA-4113: - [~mjsax] has any thought been given to making the strategy for

[jira] [Commented] (KAFKA-7075) Allow Topology#addGlobalStore to add a window store

[ https://issues.apache.org/jira/browse/KAFKA-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16743104#comment-16743104 ] Tommy Becker commented on KAFKA-7075: - Any update on this?  Would be great to get this in. > Allow

[jira] [Commented] (KAFKA-7075) Allow Topology#addGlobalStore to add a window store

[ https://issues.apache.org/jira/browse/KAFKA-7075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16745164#comment-16745164 ] Tommy Becker commented on KAFKA-7075: - [~lmontrieux] I'm curious what your use-case is. After

[jira] [Created] (KAFKA-7700) AbstractConfig does not honor Properties defaults

Tommy Becker created KAFKA-7700: --- Summary: AbstractConfig does not honor Properties defaults Key: KAFKA-7700 URL: https://issues.apache.org/jira/browse/KAFKA-7700 Project: Kafka Issue Type:

[jira] [Assigned] (KAFKA-7700) AbstractConfig does not honor Properties defaults

[ https://issues.apache.org/jira/browse/KAFKA-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommy Becker reassigned KAFKA-7700: --- Assignee: (was: Tommy Becker) > AbstractConfig does not honor Properties defaults >

[jira] [Commented] (KAFKA-7700) AbstractConfig does not honor Properties defaults

[ https://issues.apache.org/jira/browse/KAFKA-7700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707618#comment-16707618 ] Tommy Becker commented on KAFKA-7700: - One option here would be to deprecate the use of

[jira] [Commented] (KAFKA-7663) Custom Processor supplied on addGlobalStore is not used when restoring state from topic

[ https://issues.apache.org/jira/browse/KAFKA-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753984#comment-16753984 ] Tommy Becker commented on KAFKA-7663: - I hit this as well; it really makes 

[jira] [Commented] (KAFKA-7872) Consider allowing transformations on GlobalKTable before materialization

[ https://issues.apache.org/jira/browse/KAFKA-7872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753989#comment-16753989 ] Tommy Becker commented on KAFKA-7872: - [~mjsax] Yes I believe it is. > Consider allowing

[jira] [Commented] (KAFKA-7397) Ability to apply DSL stateless transformation on a global table

[ https://issues.apache.org/jira/browse/KAFKA-7397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16753988#comment-16753988 ] Tommy Becker commented on KAFKA-7397: - It's also worth noting that using the given workaround, where

[jira] [Commented] (KAFKA-8143) Kafka-Streams GlobalStore cannot be read after application restart

[ https://issues.apache.org/jira/browse/KAFKA-8143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16798573#comment-16798573 ] Tommy Becker commented on KAFKA-8143: - I think this is possibly due to

[jira] [Comment Edited] (KAFKA-7663) Custom Processor supplied on addGlobalStore is not used when restoring state from topic

[ https://issues.apache.org/jira/browse/KAFKA-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16983797#comment-16983797 ] Tommy Becker edited comment on KAFKA-7663 at 11/27/19 6:25 PM: --- Thanks for

[jira] [Commented] (KAFKA-7663) Custom Processor supplied on addGlobalStore is not used when restoring state from topic

[ https://issues.apache.org/jira/browse/KAFKA-7663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16983797#comment-16983797 ] Tommy Becker commented on KAFKA-7663: - Thanks for the comment [~vvcephei] . In the reporter's

[jira] [Commented] (KAFKA-10324) Pre-0.11 consumers can get stuck when messages are downconverted from V2 format

[ https://issues.apache.org/jira/browse/KAFKA-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167431#comment-17167431 ] Tommy Becker commented on KAFKA-10324: -- Yes. See my comment above. > Pre-0.11 consumers can get

[jira] [Comment Edited] (KAFKA-10324) Pre-0.11 consumers can get stuck when messages are downconverted from V2 format

[ https://issues.apache.org/jira/browse/KAFKA-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167400#comment-17167400 ] Tommy Becker edited comment on KAFKA-10324 at 7/29/20, 5:46 PM:

[jira] [Comment Edited] (KAFKA-10324) Pre-0.11 consumers can get stuck when messages are downconverted from V2 format

[ https://issues.apache.org/jira/browse/KAFKA-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167400#comment-17167400 ] Tommy Becker edited comment on KAFKA-10324 at 7/29/20, 5:54 PM:

[jira] [Commented] (KAFKA-10324) Pre-0.11 consumers can get stuck when messages are downconverted from V2 format

[ https://issues.apache.org/jira/browse/KAFKA-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167485#comment-17167485 ] Tommy Becker commented on KAFKA-10324: -- Understood but seems like as your fetch offset approaches

[jira] [Commented] (KAFKA-10324) Pre-0.11 consumers can get stuck when messages are downconverted from V2 format

[ https://issues.apache.org/jira/browse/KAFKA-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167480#comment-17167480 ] Tommy Becker commented on KAFKA-10324: -- So is it always the case that records returned in a

[jira] [Commented] (KAFKA-10324) Pre-0.11 consumers can get stuck when messages are downconverted from V2 format

[ https://issues.apache.org/jira/browse/KAFKA-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167400#comment-17167400 ] Tommy Becker commented on KAFKA-10324: -- [~hachikuji] wrt why the broker does not seem to send

[jira] [Created] (KAFKA-10324) Pre-0.11 consumers can get stuck when messages are downconverted from V2 format

Tommy Becker created KAFKA-10324: Summary: Pre-0.11 consumers can get stuck when messages are downconverted from V2 format Key: KAFKA-10324 URL: https://issues.apache.org/jira/browse/KAFKA-10324

[jira] [Commented] (KAFKA-10324) Pre-0.11 consumers can get stuck when messages are downconverted from V2 format

[ https://issues.apache.org/jira/browse/KAFKA-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167357#comment-17167357 ] Tommy Becker commented on KAFKA-10324: -- We have some legacy applications whose consumer versions

[jira] [Commented] (KAFKA-10324) Pre-0.11 consumers can get stuck when messages are downconverted from V2 format

[ https://issues.apache.org/jira/browse/KAFKA-10324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167371#comment-17167371 ] Tommy Becker commented on KAFKA-10324: -- Thanks for the response [~ijuma]. Yes, these are Java

[jira] [Commented] (KAFKA-12317) Relax non-null key requirement for left/outer KStream joins

[ https://issues.apache.org/jira/browse/KAFKA-12317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17402213#comment-17402213 ] Tommy Becker commented on KAFKA-12317: -- At least in the case of left stream-globalTable joins, this

[jira] [Commented] (KAFKA-13197) KStream-GlobalKTable join semantics don't match documentation

[ https://issues.apache.org/jira/browse/KAFKA-13197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17402211#comment-17402211 ] Tommy Becker commented on KAFKA-13197: -- Hey [~guozhang] thanks for the response. To be clear, I'm

[jira] [Created] (KAFKA-13197) KStream-GlobalKTable join semantics don't match documentation

Tommy Becker created KAFKA-13197: Summary: KStream-GlobalKTable join semantics don't match documentation Key: KAFKA-13197 URL: https://issues.apache.org/jira/browse/KAFKA-13197 Project: Kafka

[jira] [Commented] (KAFKA-13505) Kafka Connect should respect Avro 1.10.X enum defaults spec

[ https://issues.apache.org/jira/browse/KAFKA-13505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17817385#comment-17817385 ] Tommy Becker commented on KAFKA-13505: -- I'm wondering if this bug is being overlooked because it's

[jira] [Created] (KAFKA-16018) KafkaStreams can go into a zombie state if UncaughtExceptionHandler is specified via the deprecated method

Tommy Becker created KAFKA-16018: Summary: KafkaStreams can go into a zombie state if UncaughtExceptionHandler is specified via the deprecated method Key: KAFKA-16018 URL:

[jira] [Commented] (KAFKA-16018) KafkaStreams can go into a zombie state if UncaughtExceptionHandler is specified via the deprecated method

[ https://issues.apache.org/jira/browse/KAFKA-16018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798636#comment-17798636 ] Tommy Becker commented on KAFKA-16018: -- I think that's true, but wasn't sure on the timing of 4.0.