-
Notifications
You must be signed in to change notification settings - Fork 2.4k
[CALCITE-4114] Remove method CalciteAssert.forceDecorrelate (Jiatao Tao) #2073
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
Conversation
51441bd
to
d6f3646
Compare
final RelBuilder b = RelBuilder.create(config); | ||
pair.right.set(CalcitePrepare.Query.of(relFn.apply(b))); | ||
}); | ||
} | ||
|
||
/** Creates a {@link FrameworkConfig} that does not decorrelate. */ | ||
private FrameworkConfig forceDecorrelate(FrameworkConfig config) { | ||
private FrameworkConfig withDecorrelate(FrameworkConfig config, boolean needDecorrelate) { | ||
return Frameworks.newConfigBuilder(config) |
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.
How about just remove the method and inline the code, the method name is mis-leading.
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.
How about just remove the method and inline the code, the method name is mis-leading.
👌 agree
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.
How about just remove the method and inline the code, the method name is mis-leading.
Revised
Please also change the commit message. |
Thanks, revised. |
The origin method name is "forceDecorrelate", but what it does actually is not decorrelate, so change it.