You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During debugging incorrect TPCDS queries in #613, these incorrect rows are not ordered as Spark.
I found that the order of returned rows are not related to the sorting columns. For example, if you sort on [a, b], there are some rows with same [a, b] so the order of these rows are irrelevant to the sorting order, i.e., either
|a|b|c|
|0|1|1|
|0|1|2|
or
|a|b|c|
|0|1|2|
|0|1|1|
are correct results for sorting on [a, b]. In these failed queries, Spark sort produces one and DataFusion sort produces another one. Because we compare the results as string, they are considered incorrect now by CometTPCDSQuerySuite.
Describe the potential solution
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
What is the problem the feature request solves?
During debugging incorrect TPCDS queries in #613, these incorrect rows are not ordered as Spark.
I found that the order of returned rows are not related to the sorting columns. For example, if you sort on [a, b], there are some rows with same [a, b] so the order of these rows are irrelevant to the sorting order, i.e., either
or
are correct results for sorting on [a, b]. In these failed queries, Spark sort produces one and DataFusion sort produces another one. Because we compare the results as string, they are considered incorrect now by
CometTPCDSQuerySuite
.Describe the potential solution
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: