You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 28, 2021. It is now read-only.
The following actions should be implemented as analyzer rules to be able to parallelize queries:
If parallelization is > 1, we can introduce an Exchange node, if not, the rule is doing nothing.
Exchange nodes should be added on top of much nodes as possible.
We stop adding nodes inside Exchange node when we found a binary node or the last node with no parents. We must also stop adding nodes inside Exchange node if we find an Aggregation. In the future, we can parallelize that kind of nodes too.
We cannot add Exchange nodes on top of other Exchange nodes, but we can have several Exchange nodes on siblings (see example graph).
Exchange nodes must finish always in a table.
The text was updated successfully, but these errors were encountered:
mcarmonaa
changed the title
Partitions: Rules to apply Exange operator into query trees
Partitions: Rules to apply Exchange operator into query trees
Aug 1, 2018
The following actions should be implemented as analyzer rules to be able to parallelize queries:
If parallelization is > 1, we can introduce an Exchange node, if not, the rule is doing nothing.
Exchange nodes should be added on top of much nodes as possible.
We stop adding nodes inside Exchange node when we found a binary node or the last node with no parents. We must also stop adding nodes inside Exchange node if we find an Aggregation. In the future, we can parallelize that kind of nodes too.
We cannot add Exchange nodes on top of other Exchange nodes, but we can have several Exchange nodes on siblings (see example graph).
Exchange nodes must finish always in a table.
The text was updated successfully, but these errors were encountered: