Predicates Overview - 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 application of predicates in a query throws out the rows that do not satisfy the criterion of the predicate. Typically, the application of predicates results in reduction in number of rows. As a result, it is desirable to apply predicates as early in the query processing as possible.

At the start of Collaborative Planning, all the predicates in the surrounding query are applied on the output results produced by the SQL-MapReduce function and are therefore called onOutput predicates.

Collaborative Planning allows a SQL-MapReduce function to push an onOutput predicate to the function or input by classifying it as an byFunction or onInput predicate, respectively.

Categories to which an OnOutput predicate can be pushed
Predicate Category Description
onInput An onOutput predicate can be pushed to the function’s inputs.
byFunction An onOutput predicate can be pushed to the function, and then applied by the function itself in its processing.