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

[Subtask] Separate FilesetCatalog, TableCatalog for connector and client #3629

Closed
shaofengshi opened this issue May 29, 2024 · 1 comment
Closed
Assignees
Labels
subtask Subtasks of umbrella issue

Comments

@shaofengshi
Copy link
Contributor

Describe the subtask

The server side and client side need different API for FilesetCatalog, TableCatalog; so will separate today's one interface class to two interface classes;

Parent issue

##3626

@shaofengshi
Copy link
Contributor Author

Now I think the interface of FilesetCatalog, TableCatalog are clear, can be used for both server side and client sider, especially after we make the "NameIdentifier" class as a generic object. So close this issue for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subtask Subtasks of umbrella issue
Projects
None yet
Development

No branches or pull requests

1 participant