org.apache.drill.exec.physical.impl.project

Class TestProjectEmitOutcome

java.lang.Object

DrillTest

org.apache.drill.exec.ExecTest

org.apache.drill.test.PhysicalOpUnitTestBase

org.apache.drill.exec.physical.impl.BaseTestOpBatchEmitOutcome

org.apache.drill.exec.physical.impl.project.TestProjectEmitOutcome

public class TestProjectEmitOutcome
extends BaseTestOpBatchEmitOutcome

Nested Class Summary

Nested classes/interfaces inherited from class org.apache.drill.test.PhysicalOpUnitTestBase

PhysicalOpUnitTestBase.BatchIterator, PhysicalOpUnitTestBase.MockExecutorFragmentContext, PhysicalOpUnitTestBase.MockPhysicalOperator

Field Summary

Fields inherited from class org.apache.drill.exec.physical.impl.BaseTestOpBatchEmitOutcome

emptyInputRowSet, inputContainer, inputContainerSv2, inputOutcomes, inputSchema, nonEmptyInputRowSet, outputRecordCount

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

classpathScan, dirTestWatcher, drillbitContext, drillConf, fragContext, opContext, opCreatorReg, operatorFixture, scanDecodeExecutor, scanExecutor

Fields inherited from class org.apache.drill.exec.ExecTest

c, optionManager

Constructor Summary

Constructors

Constructor and Description
TestProjectEmitOutcome()

Method Summary

Modifier and Type	Method and Description
void	testProjectEmptyBatchEmitOutcome() Test that if empty input batch is received with OK_NEW_SCHEMA or EMIT outcome, then Project doesn't ignores these empty batches and instead return them downstream with correct outcomes.
void	testProjectNonEmptyBatchEmitOutcome() Test to show if a non-empty batch is accompanied with EMIT outcome then Project operator produces output for that batch and return the output using EMIT outcome.
void	testProjectNonEmptyFirst_EmptyBatchEmitOutcome() Test to show that non-empty first batch produces output for that batch with OK_NEW_SCHEMA and later empty batch with EMIT outcome is also passed through rather than getting ignored.
void	testProjectNonEmptyFirst_EmptyOK_EmptyBatchEmitOutcome() Test to show if an empty batch is accompanied with OK outcome then that batch is ignored by Project operator and it doesn't return anything instead call's next() to get another batch.
void	testProjectWithComplexWritersAndEmitOutcome_EmptyFirstBatch() Test to show that in cases with functions in project list whose output is complex types, if Project sees an EMIT outcome then it fails.
void	testProjectWithComplexWritersAndEmitOutcome_NonEmptyFirstBatch() Test to show that in cases with functions in project list whose output is complex types, if Project sees an EMIT outcome then it fails.

Methods inherited from class org.apache.drill.exec.physical.impl.BaseTestOpBatchEmitOutcome

afterTest, beforeTest, setUpBeforeClass

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

getJsonReadersFromBatchString, getJsonReadersFromInputFiles, getOpCreatorReg, getReaderListForJsonBatches, joinCond, legacyOpTestBuilder, mockFragmentContext, mockOpContext, opTestBuilder, ordering, parseExprs, setup, teardown

Methods inherited from class org.apache.drill.exec.ExecTest

clear, getLocalFileSystem, mockDrillbitContext, mockUsDateFormatSymbols, mockUtcDateTimeZone, parseExpr, setupOptionManager

Methods inherited from class java.lang.Object

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

Constructor Detail

TestProjectEmitOutcome

public TestProjectEmitOutcome()

Method Detail

testProjectEmptyBatchEmitOutcome

public void testProjectEmptyBatchEmitOutcome()
                                      throws Throwable

Test that if empty input batch is received with OK_NEW_SCHEMA or EMIT outcome, then Project doesn't ignores these empty batches and instead return them downstream with correct outcomes.

Throws:

Throwable

testProjectNonEmptyBatchEmitOutcome

public void testProjectNonEmptyBatchEmitOutcome()
                                         throws Throwable

Test to show if a non-empty batch is accompanied with EMIT outcome then Project operator produces output for that batch and return the output using EMIT outcome.

Throws:

Throwable

testProjectNonEmptyFirst_EmptyBatchEmitOutcome

public void testProjectNonEmptyFirst_EmptyBatchEmitOutcome()
                                                    throws Throwable

Test to show that non-empty first batch produces output for that batch with OK_NEW_SCHEMA and later empty batch with EMIT outcome is also passed through rather than getting ignored.

Throws:

Throwable

testProjectNonEmptyFirst_EmptyOK_EmptyBatchEmitOutcome

public void testProjectNonEmptyFirst_EmptyOK_EmptyBatchEmitOutcome()
                                                            throws Throwable

Test to show if an empty batch is accompanied with OK outcome then that batch is ignored by Project operator and it doesn't return anything instead call's next() to get another batch. If the subsequent next() call returns empty batch with EMIT outcome then Project returns the EMIT outcome correctly rather than ignoring it because of empty batch.

Throws:

Throwable

testProjectWithComplexWritersAndEmitOutcome_NonEmptyFirstBatch

public void testProjectWithComplexWritersAndEmitOutcome_NonEmptyFirstBatch()
                                                                    throws Throwable

Test to show that in cases with functions in project list whose output is complex types, if Project sees an EMIT outcome then it fails. This scenario can happen when complex functions are used in subquery between LATERAL and UNNEST. In which case guidance is to use those functions in project list of outermost query. Below test passes first batch as non-empty with OK_NEW_SCHEMA during which complex writers are cached for projected columns and later when an empty batch arrives with EMIT outcome the exception is thrown.

Throws:

Throwable

testProjectWithComplexWritersAndEmitOutcome_EmptyFirstBatch

public void testProjectWithComplexWritersAndEmitOutcome_EmptyFirstBatch()
                                                                 throws Throwable

Test to show that in cases with functions in project list whose output is complex types, if Project sees an EMIT outcome then it fails. This scenario can happen when complex functions are used in subquery between LATERAL and UNNEST. In which case guidance is to use those functions in project list of outermost query. Below test passes first batch as empty with OK_NEW_SCHEMA during which complex writers are not known so far and Project calls next() on upstream to get a batch with data. But later when an empty batch arrives with EMIT outcome the exception is thrown as the scenario is not supported

Throws:

Throwable