[jira] [Updated] (KAFKA-9744) SchemaProjector fails to handle backwards-compatible schema change

[ https://issues.apache.org/jira/browse/KAFKA-9744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jurgis Pods updated KAFKA-9744: --- Description: _Note_: This bug report is for CP 5.3.1 / Kafka 2.3.1, but it most likely affects all v

[jira] [Updated] (KAFKA-9744) SchemaProjector fails to handle change of record namespace in Avro schema

[ https://issues.apache.org/jira/browse/KAFKA-9744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jurgis Pods updated KAFKA-9744: --- Summary: SchemaProjector fails to handle change of record namespace in Avro schema (was: SchemaProje

[jira] [Updated] (KAFKA-9744) SchemaProjector fails to handle change of record namespace in Avro schema

[ https://issues.apache.org/jira/browse/KAFKA-9744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jurgis Pods updated KAFKA-9744: --- Description: _Note_: This bug report is for CP 5.3.1 / Kafka 2.3.1, but it most likely affects all v

[jira] [Commented] (KAFKA-9744) SchemaProjector fails to handle change of record namespace in Avro schema

[ https://issues.apache.org/jira/browse/KAFKA-9744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080426#comment-17080426 ] Jurgis Pods commented on KAFKA-9744: I've updated my bug report to be more clear. In

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's timestamp is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Summary: Kafka timestamp-based retention policy is not working when Kafka client's timestamp is not

[jira] [Commented] (KAFKA-9846) Race condition can lead to severe lag underestimate for active tasks

[ https://issues.apache.org/jira/browse/KAFKA-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080554#comment-17080554 ] Vinoth Chandar commented on KAFKA-9846: --- hi [~ableegoldman], if you were talking ab

[jira] [Resolved] (KAFKA-6910) Ability to specify a default state store type or factory

[ https://issues.apache.org/jira/browse/KAFKA-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6910. Resolution: Duplicate > Ability to specify a default state store type or factory >

[jira] [Assigned] (KAFKA-9323) Refactor Streams' upgrade system tests

[ https://issues.apache.org/jira/browse/KAFKA-9323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nikolay Izhikov reassigned KAFKA-9323: -- Assignee: (was: Nikolay Izhikov) > Refactor Streams' upgrade system tests > -

[jira] [Created] (KAFKA-9850) Move KStream#repartition operator validation during Topology build process

Levani Kokhreidze created KAFKA-9850: Summary: Move KStream#repartition operator validation during Topology build process Key: KAFKA-9850 URL: https://issues.apache.org/jira/browse/KAFKA-9850 Pro

[jira] [Commented] (KAFKA-9846) Race condition can lead to severe lag underestimate for active tasks

[ https://issues.apache.org/jira/browse/KAFKA-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080636#comment-17080636 ] Sophie Blee-Goldman commented on KAFKA-9846: True, the literal Task.State was

[jira] [Created] (KAFKA-9851) Revoking Connect tasks due to connectivity issues should also clear running assignment

Konstantine Karantasis created KAFKA-9851: - Summary: Revoking Connect tasks due to connectivity issues should also clear running assignment Key: KAFKA-9851 URL: https://issues.apache.org/jira/browse/KAFKA-

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's timestamp is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Description: what's the issue? we have log retention with 12 hours. there are log segments not del

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's timestamp is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Description: what's the issue? {quote}we have log retention with 12 hours. there are log segments n

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's timestamp is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Description: What's the issue and impact? {quote}We have log retention with 12 hours. there are log

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's timestamp is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Description: What's the issue? {quote}We have log retention with 12 hours. there are log segments n

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Summary: Kafka timestamp-based retention policy is not working when Kafka client's time is not reli

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Affects Version/s: 1.1.1 > Kafka timestamp-based retention policy is not working when Kafka client'

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Component/s: logging log cleaner > Kafka timestamp-based retention policy is not w

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Description: What's the issue? {quote}There were log segments, which can not deleted after over con

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Description: What's the issue? {quote}There were log segments, which can not be deleted over config

[jira] [Comment Edited] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822636#comment-16822636 ] Jiangtao Liu edited comment on KAFKA-8270 at 4/10/20, 5:53 PM:

[jira] [Commented] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080665#comment-17080665 ] Jiangtao Liu commented on KAFKA-8270: - Anyone if you have or may run into the issue,

[jira] [Comment Edited] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080665#comment-17080665 ] Jiangtao Liu edited comment on KAFKA-8270 at 4/10/20, 5:57 PM:

[jira] [Comment Edited] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080665#comment-17080665 ] Jiangtao Liu edited comment on KAFKA-8270 at 4/10/20, 5:58 PM:

[jira] [Commented] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080668#comment-17080668 ] Jiangtao Liu commented on KAFKA-8270: - Please comment me if you need to have more con

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Description: What's the issue? {quote}There were log segments, which can not be deleted over config

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Description: What's the issue? {quote}There were log segments, which can not be deleted over config

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Description: What's the issue? {quote}There were log segments, which can not be deleted over config

[jira] [Updated] (KAFKA-8270) Kafka timestamp-based retention policy is not working when Kafka client's time is not reliable.

[ https://issues.apache.org/jira/browse/KAFKA-8270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiangtao Liu updated KAFKA-8270: Description: I have a particular blog to explain the whole context at here  [https://medium.com/@ji

[jira] [Commented] (KAFKA-6145) Warm up new KS instances before migrating tasks - potentially a two phase rebalance

[ https://issues.apache.org/jira/browse/KAFKA-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080851#comment-17080851 ] ASF GitHub Bot commented on KAFKA-6145: --- vvcephei commented on pull request #8436:

[jira] [Commented] (KAFKA-9832) Extend EOS system tests for EOS-beta

[ https://issues.apache.org/jira/browse/KAFKA-9832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080856#comment-17080856 ] ASF GitHub Bot commented on KAFKA-9832: --- mjsax commented on pull request #8443: KAF

[jira] [Commented] (KAFKA-9592) Safely abort Producer transactions during application shutdown

[ https://issues.apache.org/jira/browse/KAFKA-9592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080875#comment-17080875 ] Guozhang Wang commented on KAFKA-9592: -- I would think so: the current javadoc of abo

[jira] [Commented] (KAFKA-9603) Number of open files keeps increasing in Streams application

[ https://issues.apache.org/jira/browse/KAFKA-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080887#comment-17080887 ] Guozhang Wang commented on KAFKA-9603: -- Great, thanks! I'd be waiting for you to sha

[jira] [Assigned] (KAFKA-4668) Mirrormaker should default to auto.offset.reset=earliest

[ https://issues.apache.org/jira/browse/KAFKA-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Widman reassigned KAFKA-4668: -- Assignee: Jeff Widman > Mirrormaker should default to auto.offset.reset=earliest > ---

[jira] [Commented] (KAFKA-9846) Race condition can lead to severe lag underestimate for active tasks

[ https://issues.apache.org/jira/browse/KAFKA-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080978#comment-17080978 ] ASF GitHub Bot commented on KAFKA-9846: --- vinothchandar commented on pull request #8

[jira] [Updated] (KAFKA-9642) "BigDecimal(double)" should not be used

[ https://issues.apache.org/jira/browse/KAFKA-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantine Karantasis updated KAFKA-9642: -- Fix Version/s: 2.6.0 > "BigDecimal(double)" should not be used > --

[jira] [Commented] (KAFKA-9846) Race condition can lead to severe lag underestimate for active tasks

[ https://issues.apache.org/jira/browse/KAFKA-9846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17080989#comment-17080989 ] Vinoth Chandar commented on KAFKA-9846: --- Understood, I was always wary of grabbing

[jira] [Commented] (KAFKA-8124) Beginning offset is after the ending offset for topic partition

[ https://issues.apache.org/jira/browse/KAFKA-8124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081023#comment-17081023 ] Rishabh commented on KAFKA-8124: +1 > Beginning offset is after the ending offset for to

[jira] [Commented] (KAFKA-3720) Remove BufferExhaustedException from doSend() in KafkaProducer

[ https://issues.apache.org/jira/browse/KAFKA-3720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081045#comment-17081045 ] ASF GitHub Bot commented on KAFKA-3720: --- junrao commented on pull request #8399: KA

[jira] [Created] (KAFKA-9852) Lower block duration in BufferPoolTest to cut down on overall test runtime

Sönke Liebau created KAFKA-9852: --- Summary: Lower block duration in BufferPoolTest to cut down on overall test runtime Key: KAFKA-9852 URL: https://issues.apache.org/jira/browse/KAFKA-9852 Project: Kafka

[jira] [Commented] (KAFKA-9852) Lower block duration in BufferPoolTest to cut down on overall test runtime

[ https://issues.apache.org/jira/browse/KAFKA-9852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081052#comment-17081052 ] ASF GitHub Bot commented on KAFKA-9852: --- soenkeliebau commented on pull request #84

[jira] [Commented] (KAFKA-9852) Lower block duration in BufferPoolTest to cut down on overall test runtime

[ https://issues.apache.org/jira/browse/KAFKA-9852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081056#comment-17081056 ] Sönke Liebau commented on KAFKA-9852: - [~junrao] as just discussed in the [PR|https:

[jira] [Commented] (KAFKA-9765) Could not add partitions to transaction due to errors

[ https://issues.apache.org/jira/browse/KAFKA-9765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081060#comment-17081060 ] Guozhang Wang commented on KAFKA-9765: -- Hello [~waykarp] I looked your uploaded stac

[jira] [Commented] (KAFKA-4668) Mirrormaker should default to auto.offset.reset=earliest

[ https://issues.apache.org/jira/browse/KAFKA-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081137#comment-17081137 ] Jeff Widman commented on KAFKA-4668: Going to try to get this across the line, three

[jira] [Comment Edited] (KAFKA-4668) Mirrormaker should default to auto.offset.reset=earliest

[ https://issues.apache.org/jira/browse/KAFKA-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081137#comment-17081137 ] Jeff Widman edited comment on KAFKA-4668 at 4/11/20, 4:44 AM: -

[jira] [Comment Edited] (KAFKA-4668) Mirrormaker should default to auto.offset.reset=earliest

[ https://issues.apache.org/jira/browse/KAFKA-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17081137#comment-17081137 ] Jeff Widman edited comment on KAFKA-4668 at 4/11/20, 4:44 AM: -