org.apache.drill.exec.physical.impl.limit

Class TestLimitBatchEmitOutcome

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.limit.TestLimitBatchEmitOutcome

public class TestLimitBatchEmitOutcome
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
TestLimitBatchEmitOutcome()

Method Summary

Modifier and Type	Method and Description
void	testLimitEmptyBatchEmitOutcome() Test to show empty batch with both OK_NEW_SCHEMA and EMIT outcome is not ignored by Limit and is pass through to the downstream operator.
void	testLimitNonEmptyBatchEmitOutcome() Test to validate limit considers all the data until it sees EMIT outcome and return output batch with data that meets the limit criteria.
void	testLimitNonEmptyFirst_EmptyOKEmitOutcome() Test to show that when the limit number of records is found with first incoming batch, then next empty incoming batch with OK outcome is ignored, but the empty EMIT outcome batch is not ignored.
void	testLimitNonEmptyFirst_NonEmptyOK_EmptyBatchEmitOutcome() Test shows that limit operates on multiple input batches until it finds limit number of records or it sees an EMIT outcome to refresh it's state.
void	testLimitResetsAfterFirstEmitOutcome() Test to show that once a limit number of records is produced using first set of batches then on getting a batch with EMIT outcome, the limit state is again refreshed and applied to next set of batches with data.
void	testMultipleLimitWithEMITOutcome() Test to show that limit refreshes it's state after seeing first EMIT outcome and works on data batches following it as new set's of incoming batch and apply the limits rule from fresh on those.

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

TestLimitBatchEmitOutcome

public TestLimitBatchEmitOutcome()

Method Detail

testLimitEmptyBatchEmitOutcome

public void testLimitEmptyBatchEmitOutcome()
                                    throws Throwable

Test to show empty batch with both OK_NEW_SCHEMA and EMIT outcome is not ignored by Limit and is pass through to the downstream operator.

Throws:

Throwable

testLimitNonEmptyBatchEmitOutcome

public void testLimitNonEmptyBatchEmitOutcome()
                                       throws Throwable

Test to validate limit considers all the data until it sees EMIT outcome and return output batch with data that meets the limit criteria.

Throws:

Throwable

testLimitResetsAfterFirstEmitOutcome

public void testLimitResetsAfterFirstEmitOutcome()
                                          throws Throwable

Test to show that once a limit number of records is produced using first set of batches then on getting a batch with EMIT outcome, the limit state is again refreshed and applied to next set of batches with data.

Throws:

Throwable

testLimitNonEmptyFirst_EmptyOKEmitOutcome

public void testLimitNonEmptyFirst_EmptyOKEmitOutcome()
                                               throws Throwable

Test to show that when the limit number of records is found with first incoming batch, then next empty incoming batch with OK outcome is ignored, but the empty EMIT outcome batch is not ignored. Empty incoming batch with EMIT outcome produces empty output batch with EMIT outcome.

Throws:

Throwable

testMultipleLimitWithEMITOutcome

public void testMultipleLimitWithEMITOutcome()
                                      throws Throwable

Test to show that limit refreshes it's state after seeing first EMIT outcome and works on data batches following it as new set's of incoming batch and apply the limits rule from fresh on those. So for first set of batches with OK_NEW_SCHEMA and EMIT outcome but total number of records received being less than limit condition, it still produces an output with that many records (in this case 1 even though limit number of records is 2).

After seeing EMIT, it refreshes it's state and operate on next input batches to again return limit number of records. So for 3rd batch with 2 records but with EMIT outcome it produces an output batch with 2 records not with 1 since state is refreshed.

Throws:

Throwable

testLimitNonEmptyFirst_NonEmptyOK_EmptyBatchEmitOutcome

public void testLimitNonEmptyFirst_NonEmptyOK_EmptyBatchEmitOutcome()
                                                             throws Throwable

Test shows that limit operates on multiple input batches until it finds limit number of records or it sees an EMIT outcome to refresh it's state.

Throws:

Throwable