LuciferYang commented on code in PR #12981:
URL: https://github.com/apache/gluten/pull/12981#discussion_r3969495364


##########
backends-clickhouse/src/test/scala/org/apache/gluten/execution/GlutenFunctionValidateSuite.scala:
##########
@@ -699,17 +699,10 @@ class GlutenFunctionValidateSuite extends 
GlutenClickHouseWholeStageTransformerS
   }
 
   test("test common subexpression eliminate") {
+    // TODO: the expected operator counts at the call sites below only held on 
Spark 3.3. Re-derive
+    // them for the supported versions and turn this back into a real 
assertion.
     def checkOperatorCount[T <: TransformSupport](count: Int)(df: 
DataFrame)(implicit
-        tag: ClassTag[T]): Unit = {
-      if (spark33) {
-        assert(
-          getExecutedPlan(df).count(
-            plan => {
-              plan.getClass == tag.runtimeClass
-            }) == count,
-          s"executed plan: ${getExecutedPlan(df)}")
-      }
-    }
+        tag: ClassTag[T]): Unit = {}

Review Comment:
   Agreed on the substance, and this is now tracked in #12988 together with the 
thirteen permanently-ignored ClickHouse cases, since it is the same kind of 
call.
   
   I left it alone in this PR deliberately. Restoring the assertions needs the 
expected operator counts re-derived on a supported version, which needs a 
ClickHouse run I cannot do here, and converting the enclosing tests to `ignore` 
drops coverage that @zzcclp should weigh rather than a version-check cleanup. 
Your `pendingUntilFixed` suggestion is a good third option and I have not seen 
it used in this repo yet; worth raising on the issue.
   
   Keeping the call sites and their counts behind the TODO is what preserves 
the only record of what the plan used to look like, which is why I did not just 
delete the helper.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to