-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
[Data] Add rule for ReorderRandomizeBlockOrder
#32254
Conversation
Signed-off-by: amogkam <amogkamsetty@yahoo.com>
return LogicalPlan(dag=optimized_dag) | ||
|
||
def _apply(self, op: LogicalOperator) -> LogicalOperator: | ||
seeds = [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as discussed, let's keep a list of RandomizeBlocks
operator, instead of seed
, to be future-proof when we add more attributes into RandomizeBlocks
. Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
RandomizeBlockOrder
ReorderRandomizeBlockOrder
Ports over previous rule to move RandomizeBlockOrder to the end of a DAG into the new execution backend as an optimizer rule. Closes ray-project#31894 Signed-off-by: amogkam <amogkamsetty@yahoo.com> Signed-off-by: Edward Oakes <ed.nmi.oakes@gmail.com>
Ports over previous rule to move
RandomizeBlockOrder
to the end of a DAG into the new execution backend as an optimizer rule.Closes #31894
Why are these changes needed?
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.