org.apache.drill.exec.physical.resultSet.impl

Class TestResultSetSchemaChange

java.lang.Object

DrillTest

org.apache.drill.test.SubOperatorTest

org.apache.drill.exec.physical.resultSet.impl.TestResultSetSchemaChange

public class TestResultSetSchemaChange
extends SubOperatorTest

Field Summary

Fields inherited from class org.apache.drill.test.SubOperatorTest

dirTestWatcher, fixture

Constructor Summary

Constructors

Constructor and Description
TestResultSetSchemaChange()

Method Summary

Modifier and Type	Method and Description
void	testSchemaChangeFirstBatch() Test the case where the schema changes in the first batch.
void	testSchemaChangeWithOverflow() Test a schema change on the row that overflows.

Methods inherited from class org.apache.drill.test.SubOperatorTest

classSetup, classTeardown

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

TestResultSetSchemaChange

public TestResultSetSchemaChange()

Method Detail

testSchemaChangeFirstBatch

public void testSchemaChangeFirstBatch()

Test the case where the schema changes in the first batch. Schema changes before the first record are trivial and tested elsewhere. Here we write some records, then add new columns, as a JSON reader might do.

testSchemaChangeWithOverflow

public void testSchemaChangeWithOverflow()

Test a schema change on the row that overflows. If the new column is added after overflow, it will appear as a schema-change in the following batch. This is fine as we are essentially time-shifting: pretending that the overflow row was written in the next batch (which, in fact, it is: that's what overflow means.)