[jira] [Commented] (KAFKA-16141) StreamsStandbyTask##test_standby_tasks_rebalanceArguments:{ “metadata_quorum”: “ISOLATED_KRAFT”, “use_new_coordinator”: false} fails consistently in 3.7

[ https://issues.apache.org/jira/browse/KAFKA-16141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807520#comment-17807520 ] Almog Gavra commented on KAFKA-16141: - OK, after doing some more digging I don't think it's related

[jira] [Commented] (KAFKA-16141) StreamsStandbyTask##test_standby_tasks_rebalanceArguments:{ “metadata_quorum”: “ISOLATED_KRAFT”, “use_new_coordinator”: false} fails consistently in 3.7

[ https://issues.apache.org/jira/browse/KAFKA-16141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17807434#comment-17807434 ] Almog Gavra commented on KAFKA-16141: - I confirmed it’s most likely related to my change - changing

[jira] [Commented] (KAFKA-16046) Stream Stream Joins fail after restoration with deserialization exceptions

[ https://issues.apache.org/jira/browse/KAFKA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17801904#comment-17801904 ] Almog Gavra commented on KAFKA-16046: - https://github.com/apache/kafka/pull/15073 > Stream Stream

[jira] [Reopened] (KAFKA-16046) Stream Stream Joins fail after restoration with deserialization exceptions

[ https://issues.apache.org/jira/browse/KAFKA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra reopened KAFKA-16046: - > Stream Stream Joins fail after restoration with deserialization exceptions >

[jira] [Resolved] (KAFKA-16046) Stream Stream Joins fail after restoration with deserialization exceptions

[ https://issues.apache.org/jira/browse/KAFKA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra resolved KAFKA-16046. - Resolution: Fixed > Stream Stream Joins fail after restoration with deserialization exceptions

[jira] [Updated] (KAFKA-16046) Stream Stream Joins fail after restoration with deserialization exceptions

[ https://issues.apache.org/jira/browse/KAFKA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra updated KAFKA-16046: Labels: streams (was: ) > Stream Stream Joins fail after restoration with deserialization

[jira] [Updated] (KAFKA-16046) Stream Stream Joins fail after restoration with deserialization exceptions

[ https://issues.apache.org/jira/browse/KAFKA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra updated KAFKA-16046: Component/s: streams > Stream Stream Joins fail after restoration with deserialization exceptions

[jira] [Created] (KAFKA-16046) Stream Stream Joins fail after restoration with deserialization exceptions

Almog Gavra created KAFKA-16046: --- Summary: Stream Stream Joins fail after restoration with deserialization exceptions Key: KAFKA-16046 URL: https://issues.apache.org/jira/browse/KAFKA-16046 Project:

[jira] [Commented] (KAFKA-16046) Stream Stream Joins fail after restoration with deserialization exceptions

[ https://issues.apache.org/jira/browse/KAFKA-16046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799623#comment-17799623 ] Almog Gavra commented on KAFKA-16046: - https://github.com/apache/kafka/pull/15061 > Stream Stream

[jira] [Updated] (KAFKA-16038) Periodic Logging of Current Assignment

[ https://issues.apache.org/jira/browse/KAFKA-16038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra updated KAFKA-16038: Summary: Periodic Logging of Current Assignment (was: Periodic Logging fo Current Assignment) >

[jira] [Created] (KAFKA-16038) Periodic Logging fo Current Assignment

Almog Gavra created KAFKA-16038: --- Summary: Periodic Logging fo Current Assignment Key: KAFKA-16038 URL: https://issues.apache.org/jira/browse/KAFKA-16038 Project: Kafka Issue Type: Improvement

[jira] (KAFKA-15215) The default.dsl.store config is not compatible with custom state stores

[ https://issues.apache.org/jira/browse/KAFKA-15215 ] Almog Gavra deleted comment on KAFKA-15215: - was (Author: agavra): Note that we decided not to have default.dsl.store work if you only pass it in to the main KafkaStreams constructor for

[jira] [Resolved] (KAFKA-15774) Respect default.dsl.store Configuration Without Passing it to StreamsBuilder

[ https://issues.apache.org/jira/browse/KAFKA-15774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra resolved KAFKA-15774. - Fix Version/s: 3.7.0 Resolution: Fixed Note that we decided not to have

[jira] [Commented] (KAFKA-15215) The default.dsl.store config is not compatible with custom state stores

[ https://issues.apache.org/jira/browse/KAFKA-15215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17788559#comment-17788559 ] Almog Gavra commented on KAFKA-15215: - Note that we decided not to have default.dsl.store work if

[jira] [Resolved] (KAFKA-15215) The default.dsl.store config is not compatible with custom state stores

[ https://issues.apache.org/jira/browse/KAFKA-15215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra resolved KAFKA-15215. - Fix Version/s: 3.7.0 Resolution: Fixed > The default.dsl.store config is not compatible

[jira] [Created] (KAFKA-15774) Respect default.dsl.store Configuration Without Passing it to StreamsBuilder

Almog Gavra created KAFKA-15774: --- Summary: Respect default.dsl.store Configuration Without Passing it to StreamsBuilder Key: KAFKA-15774 URL: https://issues.apache.org/jira/browse/KAFKA-15774 Project:

[jira] [Commented] (KAFKA-12774) kafka-streams 2.8: logging in uncaught-exceptionhandler doesn't go through log4j

[ https://issues.apache.org/jira/browse/KAFKA-12774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17352499#comment-17352499 ] Almog Gavra commented on KAFKA-12774: - I went back to triage the severity of this because if things

[jira] [Updated] (KAFKA-12192) Add Configuration to Selectively Disable Topology Optimizations

[ https://issues.apache.org/jira/browse/KAFKA-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra updated KAFKA-12192: Fix Version/s: (was: 2.8.0) > Add Configuration to Selectively Disable Topology Optimizations

[jira] [Created] (KAFKA-12192) Add Configuration to Selectively Disable Topology Optimizations

Almog Gavra created KAFKA-12192: --- Summary: Add Configuration to Selectively Disable Topology Optimizations Key: KAFKA-12192 URL: https://issues.apache.org/jira/browse/KAFKA-12192 Project: Kafka

[jira] [Commented] (KAFKA-10569) Running aggregate queries on KSQL client side is getting to ERROR Shutdown broker because all log dirs in ...

[ https://issues.apache.org/jira/browse/KAFKA-10569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17206551#comment-17206551 ] Almog Gavra commented on KAFKA-10569: - Hello [~petregor...@gmail.com] - I took a look through the

[jira] [Commented] (KAFKA-8037) KTable restore may load bad data

[ https://issues.apache.org/jira/browse/KAFKA-8037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17163135#comment-17163135 ] Almog Gavra commented on KAFKA-8037: > That said...in my (admiteddly anecdotal) experience, the

[jira] [Comment Edited] (KAFKA-8037) KTable restore may load bad data

[ https://issues.apache.org/jira/browse/KAFKA-8037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17163135#comment-17163135 ] Almog Gavra edited comment on KAFKA-8037 at 7/22/20, 11:27 PM: --- > That

[jira] [Commented] (KAFKA-8037) KTable restore may load bad data

[ https://issues.apache.org/jira/browse/KAFKA-8037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17163133#comment-17163133 ] Almog Gavra commented on KAFKA-8037: > Can you give a specific example of how things would break due

[jira] [Commented] (KAFKA-8037) KTable restore may load bad data

[ https://issues.apache.org/jira/browse/KAFKA-8037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17163021#comment-17163021 ] Almog Gavra commented on KAFKA-8037: There are lots of threads going on in this discussion, but re:

[jira] [Commented] (KAFKA-8037) KTable restore may load bad data

[ https://issues.apache.org/jira/browse/KAFKA-8037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17161440#comment-17161440 ] Almog Gavra commented on KAFKA-8037: I'm not totally sure I'm understanding the solutions, but

[jira] [Commented] (KAFKA-10179) State Store Passes Wrong Changelog Topic to Serde for Optimized Source Tables

[ https://issues.apache.org/jira/browse/KAFKA-10179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17146707#comment-17146707 ] Almog Gavra commented on KAFKA-10179: - [~ableegoldman] I confirmed locally that nothing "breaks" if

[jira] [Created] (KAFKA-8595) Support SerDe of Decimals in JSON that are not HEX encoded

Almog Gavra created KAFKA-8595: -- Summary: Support SerDe of Decimals in JSON that are not HEX encoded Key: KAFKA-8595 URL: https://issues.apache.org/jira/browse/KAFKA-8595 Project: Kafka Issue

[jira] [Commented] (KAFKA-8514) Kafka clients should not include Scala's Java 8 compatibility lib

[ https://issues.apache.org/jira/browse/KAFKA-8514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860241#comment-16860241 ] Almog Gavra commented on KAFKA-8514: [https://github.com/apache/kafka/pull/6910] - everything

[jira] [Commented] (KAFKA-8514) Kafka clients should not include Scala's Java 8 compatibility lib

[ https://issues.apache.org/jira/browse/KAFKA-8514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860099#comment-16860099 ] Almog Gavra commented on KAFKA-8514: ack. thanks for pointing this out [~ennru]! I'll change this and

[jira] [Assigned] (KAFKA-8514) Kafka clients should not include Scala's Java 8 compatibility lib

[ https://issues.apache.org/jira/browse/KAFKA-8514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra reassigned KAFKA-8514: -- Assignee: Almog Gavra > Kafka clients should not include Scala's Java 8 compatibility lib >

[jira] [Updated] (KAFKA-8305) AdminClient should support creating topics with default partitions and replication factor

[ https://issues.apache.org/jira/browse/KAFKA-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra updated KAFKA-8305: --- Summary: AdminClient should support creating topics with default partitions and replication factor

[jira] [Commented] (KAFKA-8305) AdminClient should support creating topics with default partitions and replication factor

[ https://issues.apache.org/jira/browse/KAFKA-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16837631#comment-16837631 ] Almog Gavra commented on KAFKA-8305: Approved 

[jira] [Updated] (KAFKA-8305) AdminClient should support creating topics with `default.replication.factor`

[ https://issues.apache.org/jira/browse/KAFKA-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra updated KAFKA-8305: --- Description: Today, the AdminClient creates topics by requiring a `NewTopic` object, which must

[jira] [Updated] (KAFKA-8305) AdminClient should support creating topics with `default.replication.factor`

[ https://issues.apache.org/jira/browse/KAFKA-8305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Almog Gavra updated KAFKA-8305: --- Description: Today, the AdminClient creates topics by requiring a `NewTopic` object, which must

[jira] [Created] (KAFKA-8305) AdminClient should support creating topics with `default.replication.factor`

Almog Gavra created KAFKA-8305: -- Summary: AdminClient should support creating topics with `default.replication.factor` Key: KAFKA-8305 URL: https://issues.apache.org/jira/browse/KAFKA-8305 Project: