Open ic4y opened 3 weeks ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 0.00%. Comparing base (
d3520dd
) to head (00fc1fa
). Report is 2 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
There is an issue with the logic of check write in base unit test. Please wait #6793
:mag: Description
Issue References ๐
First, I'd like to thank @wForget for the help with this issue.
When using the "save to HDFS" feature, queries ending with an
ORDER BY
sometimes lose their sort order in the results. Upon investigating the code, I discovered that when usingWITH
statements and saving SQL results withtoDF.write.save
, aWithCTE
node is generated after the Sort node. This causes thecanInsertRepartitionByExpression
check to fail, leading to an incorrectRepartition
node insertion after the Sort node, which ultimately disrupts the sort order.However, this issue does not occur when using
INSERT INTO TABLE
withWithCTE
nodes.The provided unit test can reproduce this issue, but after using
toDF.write.save
, I am unable to access the complete execution plan to assert whether aRepartition
node is present. Therefore, the current test is ineffective.Hope someone can help figure out how to write this unit test.
Describe Your Solution ๐ง
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Types of changes :bookmark:
Test Plan ๐งช
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests
Checklist ๐
Be nice. Be informative.