Skip to content

Conversation

@petermaxlee
Copy link
Contributor

What changes were proposed in this pull request?

This patch enhances SQLQueryTestSuite in two ways:

  1. SPARK-17009: Use a new SparkSession for each test case to provide stronger isolation (e.g. config changes in one test case does not impact another). That said, we do not currently isolate catalog changes.
  2. SPARK-17008: Normalize query output using sorting, inspired by HiveComparisonTest.

I also ported a few new test cases over from SQLQuerySuite.

How was this patch tested?

This is a test harness update.

@petermaxlee
Copy link
Contributor Author

@cloud-fan an update here.

There is another one I want to do to improve exception handling for negative cases that I will do in a separate pull request when I port some other tests.

@SparkQA
Copy link

SparkQA commented Aug 11, 2016

Test build #63572 has finished for PR 14590 at commit e061820.

  • This patch fails PySpark unit tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@@ -0,0 +1,10 @@
-- Automatically generated by org.apache.spark.sql.SQLQueryTestSuite
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be better to remove the package name so we don't need to change all the generated files when we move this class.

@rxin
Copy link
Contributor

rxin commented Aug 11, 2016

The failed Python test is unrelated. I'm going to merge this in master. Thanks.

@asfgit asfgit closed this in 425c7c2 Aug 11, 2016

// Create a local SparkSession to have stronger isolation between different test cases.
// This does not isolate catalog changes.
val localSparkSession = spark.newSession()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it expensive? I do remember other tests share one spark session for performance reasons.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SparkSession should be fine. SparkContext is the expensive one.

@SparkQA
Copy link

SparkQA commented Aug 11, 2016

Test build #3216 has finished for PR 14590 at commit e061820.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

asfgit pushed a commit that referenced this pull request Aug 11, 2016
…ryTestSuite.

## What changes were proposed in this pull request?
This patch enhances SQLQueryTestSuite in two ways:

1. SPARK-17009: Use a new SparkSession for each test case to provide stronger isolation (e.g. config changes in one test case does not impact another). That said, we do not currently isolate catalog changes.
2. SPARK-17008: Normalize query output using sorting, inspired by HiveComparisonTest.

I also ported a few new test cases over from SQLQuerySuite.

## How was this patch tested?
This is a test harness update.

Author: petermaxlee <[email protected]>

Closes #14590 from petermaxlee/SPARK-17008.

(cherry picked from commit 425c7c2)
Signed-off-by: Wenchen Fan <[email protected]>
@cloud-fan
Copy link
Contributor

backport to 2.0!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants