peter-toth commented on issue #26028: [SPARK-29359][SQL][TESTS] Better 
exception handling in (SQL|ThriftServer)QueryTestSuite
URL: https://github.com/apache/spark/pull/26028#issuecomment-538780313
 
 
   > Could you give us more concrete example when this PR becomes more 
meaningful? For now, this seems to be not required urgently.
   
   Currently `ThriftServerQueryTestSuite` passes on master, but it fails on one 
of my PRs (https://github.com/apache/spark/pull/23531) with this error  
(https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/111651/testReport/org.apache.spark.sql.hive.thriftserver/ThriftServerQueryTestSuite/sql_3/):
   ```
   org.scalatest.exceptions.TestFailedException: Expected "
   [Recursion level limit 100 reached but query has not exhausted, try 
increasing spark.sql.cte.recursion.level.limit
   org.apache.spark.SparkException]
   ", but got "
   [org.apache.spark.SparkException
   Recursion level limit 100 reached but query has not exhausted, try 
increasing spark.sql.cte.recursion.level.limit]
   " Result did not match for query #4 WITH RECURSIVE r(level) AS (   VALUES 
(0)   UNION ALL   SELECT level + 1 FROM r ) SELECT * FROM r
   ```
   The unexpected reversed order of expected output (error message comes first, 
then the exception class) is due to this line: 
https://github.com/apache/spark/pull/26028/files#diff-b3ea3021602a88056e52bf83d8782de8L146.
 It should not sort the expected output if there was an error during execution.
   
   Other changes belong to the second point, a minor improvement to handle 
exceptions at a common place. There is no change in generated expected result.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

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

Reply via email to