You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2019/12/09 13:20:00 UTC
[jira] [Resolved] (SPARK-30159) Fix the method calls of
QueryTest.checkAnswer
[ https://issues.apache.org/jira/browse/SPARK-30159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-30159.
----------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Issue resolved by pull request 26788
[https://github.com/apache/spark/pull/26788]
> Fix the method calls of QueryTest.checkAnswer
> ---------------------------------------------
>
> Key: SPARK-30159
> URL: https://issues.apache.org/jira/browse/SPARK-30159
> Project: Spark
> Issue Type: Task
> Components: SQL, Tests
> Affects Versions: 3.0.0
> Reporter: Gengliang Wang
> Assignee: Gengliang Wang
> Priority: Major
> Fix For: 3.0.0
>
>
> Currently, the method `checkAnswer` in Object `QueryTest` returns an optional string. It doesn't throw exceptions when errors happen.
> The actual exceptions are thrown in the trait `QueryTest`.
> However, there are some test suites that use the no-op method `QueryTest.checkAnswer` and expect it to fail test cases when the input Dataframe doesn't match the expected answer. E.g. StreamSuite, SessionStateSuite, BinaryFileFormatSuite, etc.
> We should fix this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org