-
Notifications
You must be signed in to change notification settings - Fork 256
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
Handle Kafka API_VERSIONS request #547
base: main
Are you sure you want to change the base?
Conversation
@wuchong this PR is finished, PTAL |
fluss-kafka/src/test/java/com/alibaba/fluss/kafka/KafkaRequestHandlerTest.java
Outdated
Show resolved
Hide resolved
.setMinVersion(apiKey.oldestVersion()) | ||
.setMaxVersion(apiKey.latestVersion()); | ||
if (apiKey.equals(ApiKeys.METADATA)) { | ||
// Not support TopicId |
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.
Fluss uses tableId
, a globally unique identifier of type long
, to represent a table. Would it be feasible to use tableId
as the topicId
for Kafka in the future? For instance, by converting the long
value into the leastSignificantBits
and using a constant value for the mostSignificantBits
.
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.
Support topic id will make it more complex, we have to handle the case of topic ids is not empty and topic names not empty.
But we can support it in the future, at the current stage, make it as easier as we can.
Purpose
Linked issue: close #545
Handle Kafka API_VERSIONS request
Brief change log
Tests
Tests completed
API and Format
Documentation