Skip to content

KAFKA-2626: Handle null keys and value validation properly in OffsetStorageWriter.#345

Closed
ewencp wants to merge 1 commit intoapache:trunkfrom
ewencp:kafka-2626-offset-storage-writer-null-values
Closed

KAFKA-2626: Handle null keys and value validation properly in OffsetStorageWriter.#345
ewencp wants to merge 1 commit intoapache:trunkfrom
ewencp:kafka-2626-offset-storage-writer-null-values

Conversation

@ewencp
Copy link
Contributor

@ewencp ewencp commented Oct 21, 2015

No description provided.

@gwenshap
Copy link
Contributor

2 lines of code, 56 lines of tests :)

LGTM.

@asfgit asfgit closed this in 6f2f1f9 Oct 24, 2015
@ewencp
Copy link
Contributor Author

ewencp commented Oct 24, 2015

@gwenshap That's how I roll.

abbccdda pushed a commit to abbccdda/kafka that referenced this pull request Jul 8, 2020
Add describe quorum API.

1. Add data templates
2. Consolidate fetch time and offset updates
3. Separate replica State from voter state for observers
4. Bookkeep seen observers
5. Attach topic partition to the Replicated log

Reviewers: Guozhang Wang <wangguoz@gmail.com>, Jason Gustafson <jason@confluent.io>
hachikuji pushed a commit to hachikuji/kafka that referenced this pull request Aug 5, 2020
Add describe quorum API.

1. Add data templates
2. Consolidate fetch time and offset updates
3. Separate replica State from voter state for observers
4. Bookkeep seen observers
5. Attach topic partition to the Replicated log

Reviewers: Guozhang Wang <wangguoz@gmail.com>, Jason Gustafson <jason@confluent.io>
hachikuji pushed a commit to hachikuji/kafka that referenced this pull request Aug 13, 2020
Add describe quorum API.

1. Add data templates
2. Consolidate fetch time and offset updates
3. Separate replica State from voter state for observers
4. Bookkeep seen observers
5. Attach topic partition to the Replicated log

Reviewers: Guozhang Wang <wangguoz@gmail.com>, Jason Gustafson <jason@confluent.io>
wyuka pushed a commit to wyuka/kafka that referenced this pull request Jun 16, 2022
…pache#345)

TICKET = LIKAFKA-44962
LI_DESCRIPTION =
1. Add the SumOfTopicNameLength metric to track the scalability risk of kafka clusters.
   When the metric hits the 1M limit, a vanilla zk client won't be able to read all of the topic
   names that are placed under the same /brokers/topics znode. We are currently working on using the zk pagination
   feature to get past the 1M limit. Nonetheless, it's useful to monitor this value.

2. Add minor fixes of the code base to avoid compiler warnings
EXIT_CRITERIA = N/A
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.

2 participants