Skip to content
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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

dao-jun
Copy link
Contributor

@dao-jun dao-jun commented Mar 7, 2025

Purpose

Linked issue: close #545

Handle Kafka API_VERSIONS request

Brief change log

Tests

Tests completed

API and Format

Documentation

@dao-jun dao-jun closed this Mar 11, 2025
@dao-jun dao-jun reopened this Mar 11, 2025
@dao-jun
Copy link
Contributor Author

dao-jun commented Mar 11, 2025

@wuchong this PR is finished, PTAL

@dao-jun dao-jun closed this Mar 11, 2025
@dao-jun dao-jun reopened this Mar 11, 2025
.setMinVersion(apiKey.oldestVersion())
.setMaxVersion(apiKey.latestVersion());
if (apiKey.equals(ApiKeys.METADATA)) {
// Not support TopicId
Copy link
Member

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.

Copy link
Contributor Author

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.

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.

Support Kafka protocol 2: Handle API_VERSIONS request
2 participants