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.

Sign up for GitHub

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

Jump to bottom

[Question] Why does ballista store tables in the client instead of in the SchedulerServer #1473

Closed
EricJoy2048 opened this issue Dec 22, 2021 · 0 comments
Closed

[Question] Why does ballista store tables in the client instead of in the SchedulerServer #1473

EricJoy2048 opened this issue Dec 22, 2021 · 0 comments

Comments

@EricJoy2048
Copy link
Member

Why does ballista store tables in the client instead of in the SchedulerServer? If the tables information is stored in the SchedulerServer, each client can share these tables. This is very necessary for database scenarios where SQL is used to create tables and query。
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@EricJoy2048