You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2021/12/22 09:49:43 UTC
[GitHub] [arrow-datafusion] gaojun2048 opened a new issue #1473: [Question] Why does ballista store tables in the client instead of in the SchedulerServer
gaojun2048 opened a new issue #1473:
URL: https://github.com/apache/arrow-datafusion/issues/1473
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。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [arrow-datafusion] gaojun2048 closed issue #1473: [Question] Why does ballista store tables in the client instead of in the SchedulerServer
Posted by GitBox <gi...@apache.org>.
gaojun2048 closed issue #1473:
URL: https://github.com/apache/arrow-datafusion/issues/1473
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org