Ismael Juma created KAFKA-18646:
---
Summary: Empty records representation regression breaks librdkafka
Key: KAFKA-18646
URL: https://issues.apache.org/jira/browse/KAFKA-18646
Project: Kafka
Issue
TengYao Chi created KAFKA-18645:
---
Summary: New consumer should align close timeout handling with
classic consumer
Key: KAFKA-18645
URL: https://issues.apache.org/jira/browse/KAFKA-18645
Project: Kafka
Matthias J. Sax created KAFKA-18644:
---
Summary: Improve type safety in DSL code
Key: KAFKA-18644
URL: https://issues.apache.org/jira/browse/KAFKA-18644
Project: Kafka
Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-18643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-18643.
--
Resolution: Won't Fix
Since this is a tagged field, we can't set a terminal version.
> Set te
David Arthur created KAFKA-18643:
Summary: Set terminal version for
ApiVersionsResponse#ZkMigrationReady
Key: KAFKA-18643
URL: https://issues.apache.org/jira/browse/KAFKA-18643
Project: Kafka
Chirag Wadhwa created KAFKA-18642:
-
Summary: Increase timeouts in share_consumer_test.py system tests
Key: KAFKA-18642
URL: https://issues.apache.org/jira/browse/KAFKA-18642
Project: Kafka
Is
[
https://issues.apache.org/jira/browse/KAFKA-16540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Calvin Liu resolved KAFKA-16540.
Resolution: Fixed
> Update partitions when the min isr config is updated.
> --
David, I've filed a backport PR for KAFKA-17587 which reorganizes some test
code. This will help reduce friction when backporting integration test
changes from trunk. The risk of this PR is very minimal since it only
affects test sources. Let me know what you think.
https://github.com/apache/kafka
[
https://issues.apache.org/jira/browse/KAFKA-17894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-17894.
-
Fix Version/s: 4.1.0
Resolution: Fixed
Merged the PR to trunk.
> Additional metrics for cooperat
Jun Rao created KAFKA-18641:
---
Summary: AsyncKafkaConsumer could lose records with auto offset
commit
Key: KAFKA-18641
URL: https://issues.apache.org/jira/browse/KAFKA-18641
Project: Kafka
Issue Ty
Chia-Ping Tsai created KAFKA-18639:
--
Summary: Add @Flaky to testAdminClientApisAuthenticationFailure,
testOutdatedCoordinatorAssignment, and testThrottledProducerConsumer
Key: KAFKA-18639
URL: https://issues.apac
Apoorv Mittal created KAFKA-18640:
-
Summary: Tota[lProduce|Fetch]RequestsPerSec broker topic metric
tracks metric incorrectly
Key: KAFKA-18640
URL: https://issues.apache.org/jira/browse/KAFKA-18640
P
[
https://issues.apache.org/jira/browse/KAFKA-18474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-18474.
-
Resolution: Fixed
> Remove zkBroker tag
> ---
>
> Key: KAFKA-184
[
https://issues.apache.org/jira/browse/KAFKA-18616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jacot resolved KAFKA-18616.
-
Fix Version/s: 4.1.0
Resolution: Fixed
> Refactor DumpLogSegments's MessageParsers
>
Chris,
1) The expectation today is that we have a green PR build before merging.
This is sometimes relaxed in light of flaky tests at the discretion of the
committer merging the PR. In general, we should expect a green build before
merging a PR. This KIP does not change that requirement.
2) I exp
[
https://issues.apache.org/jira/browse/KAFKA-16372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Chen resolved KAFKA-16372.
---
Fix Version/s: 4.0.0
Resolution: Fixed
> max.block.ms behavior inconsistency with javadoc and
[
https://issues.apache.org/jira/browse/KAFKA-18590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18590.
Fix Version/s: 4.1.0
(was: 4.0.0)
Resolution: Fixed
> Cleanu
[
https://issues.apache.org/jira/browse/KAFKA-18559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18559.
Fix Version/s: 4.1.0
(was: 4.0.0)
Resolution: Fixed
> Cleanu
Heya David,
Thanks a lot for this!
Building on top of Chris's questions - does including only a subset of the
stages in the merge queue mean that while subsequent stages (i.e. tests)
can run in parallel-ish across PRs they will contain trunk + set of PRs
ahead of this one which passed the stage i
[
https://issues.apache.org/jira/browse/KAFKA-18620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison resolved KAFKA-18620.
Fix Version/s: 4.1.0
Resolution: Fixed
> Remove UnifiedLog#legacyFetchOffsetsBefore
[
https://issues.apache.org/jira/browse/KAFKA-18488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Schofield resolved KAFKA-18488.
--
Resolution: Fixed
> Additional protocol tests for share consumption
>
21 matches
Mail list logo