-
Notifications
You must be signed in to change notification settings - Fork 453
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
[Shims] Fix the code style issue of prepareWrite #8316
Conversation
Thanks for opening a pull request! Could you open an issue for this pull request on Github Issues? https://github.com/apache/incubator-gluten/issues Then could you also rename commit message and pull request title in the following format?
See also: |
Run Gluten Clickhouse CI on x86 |
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. Thanks for your fix.
conf | ||
.asInstanceOf[JobConf] | ||
.setOutputFormat(classOf[org.apache.orc.mapred.OrcOutputFormat[OrcStruct]]) | ||
|
||
if ("true" == sparkSession.sparkContext.getLocalProperty("isNativeApplicable")) { |
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.
This might be subjective though it's a bit weird to see these Yoda conditions in our Scala code base. Perhaps we could invert them (in future).
3dff1bf
to
09e3ec2
Compare
Run Gluten Clickhouse CI on x86 |
09e3ec2
to
ef0c44c
Compare
Run Gluten Clickhouse CI on x86 |
2 similar comments
Run Gluten Clickhouse CI on x86 |
Run Gluten Clickhouse CI on x86 |
ef0c44c
to
e115eb9
Compare
Run Gluten Clickhouse CI on x86 |
What changes were proposed in this pull request?
Fix the code style issue of 'prepareWrite' in Spark 3.2 and 3.3 shims.
How was this patch tested?
CI