-
Notifications
You must be signed in to change notification settings - Fork 15.4k
KAFKA-9629 Use generated protocol for Fetch API #9008
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 17 commits
56e4156
04538af
6094e4e
41d03d1
5c98083
8ca460c
3808a96
efdadc5
538ed00
155621b
89de508
7878289
701619d
82a0d46
38b2ebf
efa5450
2514f5a
e198797
cf3bf33
78cd012
507eb04
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,92 @@ | ||
| /* | ||
| * Licensed to the Apache Software Foundation (ASF) under one or more | ||
| * contributor license agreements. See the NOTICE file distributed with | ||
| * this work for additional information regarding copyright ownership. | ||
| * The ASF licenses this file to You under the Apache License, Version 2.0 | ||
| * (the "License"); you may not use this file except in compliance with | ||
| * the License. You may obtain a copy of the License at | ||
| * | ||
| * http://www.apache.org/licenses/LICENSE-2.0 | ||
| * | ||
| * Unless required by applicable law or agreed to in writing, software | ||
| * distributed under the License is distributed on an "AS IS" BASIS, | ||
| * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
| * See the License for the specific language governing permissions and | ||
| * limitations under the License. | ||
| */ | ||
|
|
||
| package org.apache.kafka.common.protocol; | ||
|
|
||
| import org.apache.kafka.common.record.BaseRecords; | ||
| import org.apache.kafka.common.record.MemoryRecords; | ||
| import org.apache.kafka.common.utils.ByteUtils; | ||
|
|
||
| import java.nio.ByteBuffer; | ||
|
|
||
| /** | ||
| * Implementation of Readable which reads from a byte buffer and can read records as {@link MemoryRecords} | ||
| * | ||
| * @see org.apache.kafka.common.requests.FetchResponse | ||
| */ | ||
| public class RecordsReader implements Readable { | ||
|
hachikuji marked this conversation as resolved.
Outdated
|
||
| private final ByteBuffer buf; | ||
|
|
||
| public RecordsReader(ByteBuffer buf) { | ||
| this.buf = buf; | ||
| } | ||
|
|
||
| @Override | ||
| public byte readByte() { | ||
| return buf.get(); | ||
| } | ||
|
|
||
| @Override | ||
| public short readShort() { | ||
| return buf.getShort(); | ||
| } | ||
|
|
||
| @Override | ||
| public int readInt() { | ||
| return buf.getInt(); | ||
| } | ||
|
|
||
| @Override | ||
| public long readLong() { | ||
| return buf.getLong(); | ||
| } | ||
|
|
||
| @Override | ||
| public double readDouble() { | ||
| return ByteUtils.readDouble(buf); | ||
| } | ||
|
|
||
| @Override | ||
| public void readArray(byte[] arr) { | ||
| buf.get(arr); | ||
| } | ||
|
|
||
| @Override | ||
| public int readUnsignedVarint() { | ||
| return ByteUtils.readUnsignedVarint(buf); | ||
| } | ||
|
|
||
| @Override | ||
| public ByteBuffer readByteBuffer(int length) { | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. More of a side question, but is this length guaranteed to be less than the buffer size? Wondering if it is worth adding range checking.
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is copied straight from ByteBufferAccessor and will probably go away in a follow-on PR. But either way, looking at it it seems it should always be in range since this is used by zero-copy byte fields in the message classes, e.g. int len = _reader.readInt();
if (len > 0) {
this.someZeroCopyField = _reader.readByteBuffer(len);
}So generally it's probably safe. In the case of a corrupt message where the length is wrong, ByteBuffer#limit will throw an error and parsing will fail. It probably would be nice to put a range check in ByteBufferAccessor so we can throw a more useful error. |
||
| ByteBuffer res = buf.slice(); | ||
| res.limit(length); | ||
|
|
||
| buf.position(buf.position() + length); | ||
|
|
||
| return res; | ||
| } | ||
|
|
||
| public BaseRecords readRecords(int length) { | ||
| if (length < 0) { | ||
| // no records | ||
| return null; | ||
| } else { | ||
| ByteBuffer recordsBuffer = readByteBuffer(length); | ||
| return MemoryRecords.readableRecords(recordsBuffer); | ||
| } | ||
| } | ||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: could probably change this to use
ifPresent