Github user cloud-fan commented on a diff in the pull request:

    https://github.com/apache/spark/pull/16674#discussion_r100906893
  
    --- Diff: 
sql/core/src/test/scala/org/apache/spark/sql/execution/SQLViewSuite.scala ---
    @@ -15,29 +15,34 @@
      * limitations under the License.
      */
     
    -package org.apache.spark.sql.hive.execution
    +package org.apache.spark.sql.execution
     
    -import org.apache.spark.sql.{AnalysisException, QueryTest, Row, SaveMode}
    +import org.apache.spark.sql._
     import org.apache.spark.sql.catalyst.TableIdentifier
     import org.apache.spark.sql.catalyst.analysis.NoSuchTableException
    -import org.apache.spark.sql.catalyst.catalog.{CatalogStorageFormat, 
CatalogTable, CatalogTableType}
    -import org.apache.spark.sql.hive.test.TestHiveSingleton
    -import org.apache.spark.sql.test.SQLTestUtils
    -import org.apache.spark.sql.types.StructType
    +import org.apache.spark.sql.test.{SharedSQLContext, SQLTestUtils}
    +
    +class SimpleSQLViewSuite extends SQLViewSuite with SharedSQLContext {
    +}
     
     /**
      * A suite for testing view related functionality.
      */
    -class SQLViewSuite extends QueryTest with SQLTestUtils with 
TestHiveSingleton {
    -  import spark.implicits._
    +abstract class SQLViewSuite extends QueryTest with SQLTestUtils {
    --- End diff --
    
    how about we make a `trait SparkSessionProvider` and make 
`SharedSparkContext` and `TestHiveSingleton` both extend it? then we can make 
`SQLViewSuite` extends `SparkSessionProvider` and fix this problem.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

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

Reply via email to