If loadTestTables is false, no test tables are loaded.
If loadTestTables is false, no test tables are loaded. Note that this flag can only be true when running in the JVM, i.e. it needs to be false when calling from Python.
(Since version 1.3.0) Use createDataFrame instead.
(Since version 1.3.0) Use createDataFrame instead.
(Since version 1.3.0) Use createDataFrame instead.
(Since version 1.3.0) Use createDataFrame instead.
(Since version 2.2.0) use sparkSession.catalog.createTable instead.
(Since version 2.2.0) use sparkSession.catalog.createTable instead.
(Since version 2.2.0) use sparkSession.catalog.createTable instead.
(Since version 2.2.0) use sparkSession.catalog.createTable instead.
(Since version 2.2.0) use sparkSession.catalog.createTable instead.
(Since version 2.2.0) use sparkSession.catalog.createTable instead.
(Since version 1.4.0) Use read.jdbc() instead.
(Since version 1.4.0) Use read.jdbc() instead.
(Since version 1.4.0) Use read.jdbc() instead.
(Since version 1.4.0) Use read.json() instead.
(Since version 1.4.0) Use read.json() instead.
(Since version 1.4.0) Use read.json() instead.
(Since version 1.4.0) Use read.json() instead.
(Since version 1.4.0) Use read.json() instead.
(Since version 1.4.0) Use read.json() instead.
(Since version 1.4.0) Use read.json() instead.
(Since version 1.4.0) Use read.json() instead.
(Since version 1.4.0) Use read.json() instead.
(Since version 1.4.0) Use read.format(source).schema(schema).options(options).load() instead.
(Since version 1.4.0) Use read.format(source).schema(schema).options(options).load() instead.
(Since version 1.4.0) Use read.format(source).options(options).load() instead.
(Since version 1.4.0) Use read.format(source).options(options).load() instead.
(Since version 1.4.0) Use read.format(source).load(path) instead.
(Since version 1.4.0) Use read.load(path) instead.
(Since version 1.4.0) Use read.parquet() instead.
A locally running test instance of Spark's Hive execution engine.
Data from testTables will be automatically loaded whenever a query is run over those tables. Calling reset will delete all tables and other state in the database, leaving the database in a "clean" state.
TestHive is singleton object version of this class because instantiating multiple copies of the hive metastore seems to lead to weird non-deterministic failures. Therefore, the execution of test cases that rely on TestHive must be serialized.