Skip to content

KAFKA-2554: change 0.8.3 to 0.9.0 in ApiVersion and other files#237

Closed
omkreddy wants to merge 1 commit into
apache:trunkfrom
omkreddy:KAFKA-2554
Closed

KAFKA-2554: change 0.8.3 to 0.9.0 in ApiVersion and other files#237
omkreddy wants to merge 1 commit into
apache:trunkfrom
omkreddy:KAFKA-2554

Conversation

@omkreddy

Copy link
Copy Markdown
Contributor

Updated the version from 0.8.3 to 0.9.0. in ApiVersion. Also updated in gradle.propeties.

@asfbot

asfbot commented Sep 24, 2015

Copy link
Copy Markdown

kafka-trunk-git-pr #524 FAILURE
Looks like there's a problem with this pull request

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it true that the version can have 4 segments? In ApiVersion.versionNameMap, it always has 3 segments.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, We can have 4 segments. But we will take first 3 segments for processing/version checks.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, isn't it a bit misleading to use 4 segments? It sounds to me like we would never want to change the protocol when bumping a the fourth segment.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We never want to change protocol on segment 4, but we want users to be able to type 0.9.0.1 without getting errors, just to make it more intuitive.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I find it less intuitive, personally. If there is no consensus, then yeah, this doesn't have to be handled in this PR.

@gwenshap

Copy link
Copy Markdown
Contributor

Changes LGTM and I'll merge after Jenkins updates with test results.

@ijuma concerns on the number of segments we support can be addressed in a separate jira, since this once just deals with the new version number.

@asfgit asfgit closed this in ac757eb Sep 24, 2015
wyuka pushed a commit to wyuka/kafka that referenced this pull request Jan 13, 2022
TICKET = LIKAFKA-9737 
LI_DESCRIPTION = Broker-side changes for pass-through solution.  This is the porting for commit 0d9c527

EXIT_CRITERIA = MANUAL ["If we no longer need pass-through support in Kafka. Only known user is KMM for venice; BrooklinMM has not enabled this everywhere."]

Co-authored-by: Lucas Wang <luwang@linkedin.com>
wyuka pushed a commit to wyuka/kafka that referenced this pull request Mar 4, 2022
TICKET = LIKAFKA-9737 
LI_DESCRIPTION = Broker-side changes for pass-through solution.  This is the porting for commit 0d9c527

EXIT_CRITERIA = MANUAL ["If we no longer need pass-through support in Kafka. Only known user is KMM for venice; BrooklinMM has not enabled this everywhere."]

Co-authored-by: Lucas Wang <luwang@linkedin.com>
wyuka pushed a commit to wyuka/kafka that referenced this pull request Mar 28, 2022
TICKET = LIKAFKA-9737 
LI_DESCRIPTION = Broker-side changes for pass-through solution.  This is the porting for commit 0d9c527

EXIT_CRITERIA = MANUAL ["If we no longer need pass-through support in Kafka. Only known user is KMM for venice; BrooklinMM has not enabled this everywhere."]

Co-authored-by: Lucas Wang <luwang@linkedin.com>
wyuka pushed a commit to wyuka/kafka that referenced this pull request Jun 16, 2022
TICKET = LIKAFKA-9737 
LI_DESCRIPTION = Broker-side changes for pass-through solution.  This is the porting for commit 0d9c527

EXIT_CRITERIA = MANUAL ["If we no longer need pass-through support in Kafka. Only known user is KMM for venice; BrooklinMM has not enabled this everywhere."]

Co-authored-by: Lucas Wang <luwang@linkedin.com>
udaynpusa pushed a commit to mapr/kafka that referenced this pull request Jan 30, 2024
jeqo pushed a commit to aiven/kafka that referenced this pull request Jan 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants