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

[Improvement]: Optimize the naming of database/table methods in catalog #2886

Closed
3 tasks done
xleoken opened this issue May 31, 2024 · 0 comments · Fixed by #2887
Closed
3 tasks done

[Improvement]: Optimize the naming of database/table methods in catalog #2886

xleoken opened this issue May 31, 2024 · 0 comments · Fixed by #2887

Comments

@xleoken
Copy link
Member

xleoken commented May 31, 2024

Search before asking

  • I have searched in the issues and found no similar issues.

What would you like to be improved?

Optimize the naming of database/table methods in AmoroCatalog and ServerCatalog.
rename boolean exists(String database); to boolean databaseExists(String database);
rename boolean exists(String database, String table); to boolean tableExists(String database, String table);

How should we improve?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Subtasks

No response

Code of Conduct

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant