-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Change display of RepartitionExec
from SortPreservingRepartitionExec to
RepartitionExec preserve_order=true`
#8129
Labels
Comments
FYI @ozankabak and @mustafasrepo and @metesynnada as this may impact you |
I wouldn't mind taking a look into this |
We are fine with this change |
Thanks @JacobOgle ! |
JacobOgle
added a commit
to JacobOgle/arrow-datafusion
that referenced
this issue
Dec 12, 2023
…to RepartitionExec preserve_order=true apache#8129
Should this be closed now that #8521 is merged? Looks like the PR description simply mis-formatted the |
Closed by #8521 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem or challenge?
Most (all?) nodes in DataFusion explain plans have the property that they are displayed with the same name as the
struct
that implements them, which makes matching explain plans to code easyHowever, a notable exception is
RepartitionExec
which is displayed sometimes asRepartitionExec
and sometimes asSortPreservingRepartitionExec
to signify it preserves the input sort order, which makes finding the relevant code harder (as there is no such code asSortPreservingRepartitionExec
)For example in the following plan
RepartitionExec and
SortPreservingRepartitionExec` are the same ExecutionPlan node:Describe the solution you'd like
I would like to change the display of
RepartitionExec
so it always looks likeRepartitionExec
and haspreserve_order=true
to follow the same pattern as the other nodes where the output of the explain plan matches the name of the code that implements it.So for example, name should always be
RepartitionExec
: https://github.com/apache/arrow-datafusion/blob/91c9d6f847eda0b5b1d01257b5c24459651d3926/datafusion/physical-plan/src/repartition/mod.rs#L373-L379And instead of
It should display like
Describe alternatives you've considered
I recommend ONLY displaying preserve_order when it is true
so when false, display like this:
Additional context
I think this is a good first issue as it is well specified and a mechanical change and would teach the person about datafusions tests. Beware, however, that this is likely to require a non trivial number of changes to expected test output.
Thanks in advance!
The text was updated successfully, but these errors were encountered: