Execution - Aster Execution Engine

Teradata Aster® Developer Guide

Product
Aster Execution Engine
Release Number
7.00.02
Published
July 2017
Language
English (United States)
Last Update
2018-04-13
dita:mapPath
xnl1494366523182.ditamap
dita:ditavalPath
Generic_no_ie_no_tempfilter.ditaval
dita:id
ffu1489104705746
lifecycle
previous
Product Category
Software

The following figure illustrates control and data flow during execution.

Control and data flow during execution

  1. The Analytic Engine constructs the SQL-MapReduce function on every vWorker.
  2. The Analytic Engine sends the completed planning contract in the CollaborativePlanning.receiveCompletedPlanningContract() method.

    The completed planning contract consists of the input properties of the chosen plan and the output properties returned by the SQL-MapReduce function, the query context, and the response to the query context from the SQL-MapReduce function.

    The nth negotiated contract is not necessarily the one sent to the function.
  3. The SQL-MapReduce function's operateOnSomeRows() or operateOnPartition() method is called.
  4. If the Drainable interface is implemented, the SQL-MapReduce function’s drainOutputRows() method is called.
    The operateOnSomeRows(), operateOnPartition(), and drainOutputRows() methods should be implemented to honour the completed planning contract.
    The Analytic Engine does not validate the application of the completed planning contract by the SQL-MapReduce function. Incorrect implementation can result in incorrect results.