KAFKA-2548; kafka-merge-pr tool fails to update JIRA with fix version 0.9.0.0#238
Closed
ijuma wants to merge 1 commit into
Closed
KAFKA-2548; kafka-merge-pr tool fails to update JIRA with fix version 0.9.0.0#238ijuma wants to merge 1 commit into
ijuma wants to merge 1 commit into
Conversation
Simplified the logic to choose the default fix version. We just hardcode it for `trunk` and try to compute it based on the branch name for the rest. Removed logic that tries to handle forked release branches as it seems to be specific to how the Spark project handles their JIRA.
|
kafka-trunk-git-pr #527 FAILURE |
Contributor
|
LGTM, thanks! |
jsancio
pushed a commit
to jsancio/kafka
that referenced
this pull request
Aug 6, 2019
omkreddy
pushed a commit
to omkreddy/kafka
that referenced
this pull request
Nov 27, 2019
This is necessary for Avro 1.9.1 compatibility given binary incompatibilities between Jackson 2.9.x and 2.10.x. Avro 1.9.1 depends on Jackson 2.9.x. Avro 1.9.2, once released, will depend on Jackson 2.10.x so we can then upgrade Jackson to 2.10.x again. It's worth noting that Apache Kafka and older releases of CP depend on Jackson 2.10.x. The former has no Avro dependency and older releases of CP depend on Avro 1.8.x, which depends on Jackson 1, a different library altogether (different Maven coordinates and different package names). Reviewers: Srini Dandu <sdandu@confluent.io>
soondenana
pushed a commit
to soondenana/kafka
that referenced
this pull request
Jan 22, 2020
This is necessary for Avro 1.9.1 compatibility given binary incompatibilities between Jackson 2.9.x and 2.10.x. Avro 1.9.1 depends on Jackson 2.9.x. Avro 1.9.2, once released, will depend on Jackson 2.10.x so we can then upgrade Jackson to 2.10.x again. It's worth noting that Apache Kafka and older releases of CP depend on Jackson 2.10.x. The former has no Avro dependency and older releases of CP depend on Avro 1.8.x, which depends on Jackson 1, a different library altogether (different Maven coordinates and different package names). Reviewers: Srini Dandu <sdandu@confluent.io>
wyuka
pushed a commit
to wyuka/kafka
that referenced
this pull request
Jan 21, 2022
…on (apache#238) TICKET = LIKAFKA-40747 LI_DESCRIPTION = A potential reason for NoOffsetForPartitionException is the transition of FetchState for partitions to any state other than INITIALIZING (e.g. offset_reset). However, there are not enough logs on the client side to see if that was the case. Add logs in the exception message to track the actual fetch state of partitions when a NoOffsetForPartitionException is thrown.
udaynpusa
pushed a commit
to mapr/kafka
that referenced
this pull request
Jan 30, 2024
udaynpusa
pushed a commit
to mapr/kafka
that referenced
this pull request
Jan 30, 2024
…the same time (apache#238)" This reverts commit 89bfdc9.
davide-armand
pushed a commit
to aiven/kafka
that referenced
this pull request
Dec 1, 2025
jeqo
pushed a commit
to aiven/kafka
that referenced
this pull request
Jan 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Simplified the logic to choose the default fix version. We just hardcode
it for
trunkand try to compute it based on the branch name for therest.
Removed logic that tries to handle forked release branches as it
seems to be specific to how the Spark project handles their JIRA.