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

Discussion: use local execution mode by default #4654

Closed
fuyufjh opened this issue Aug 16, 2022 · 2 comments
Closed

Discussion: use local execution mode by default #4654

fuyufjh opened this issue Aug 16, 2022 · 2 comments
Assignees
@liurenjie1024
Labels
type/feature

Comments

@fuyufjh
Copy link
Member

fuyufjh commented Aug 16, 2022

Because we will focus on serving queries (aka. simple, high-concurrent queries) currently
@chenzl25

This comment was marked as off-topic.

Sign in to view
@chenzl25 chenzl25 mentioned this issue Aug 17, 2022
Merged
3 tasks
@fuyufjh
Copy link
Member Author

fuyufjh commented Aug 17, 2022

I suggest that batch dml should share the same schedule logic (distributed/local) as query. Currently scheduling dml to one compute node is not enough for the following reason:

  • For insert select its input can be complex as arbitrary query.
  • For update and delete, it is crucial to support index lookup, otherwise full table scan is unacceptable.

Hmmm. Agree, but it's another problem. You may open an issue for that.

@liurenjie1024 liurenjie1024 mentioned this issue Aug 22, 2022
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@liurenjie1024 liurenjie1024

Labels
type/feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@liurenjie1024 @chenzl25 @fuyufjh