diff options
| author | msabhi <abhi.is2006@gmail.com> | 2016-12-16 14:33:11 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-12-16 14:33:11 -0500 |
| commit | 6e768a1fcbfe8c800527462d76ee49d62a64ef3c (patch) | |
| tree | 0fc688dfd93560155009d9b4602c2f6c01fdb825 | |
| parent | e8945e301aa622675b7106d8b58f30f6f9e9e2dd (diff) | |
Fixing Hive transformation flow
| -rw-r--r-- | chapter/8/big-data.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/chapter/8/big-data.md b/chapter/8/big-data.md index 018894d..2590095 100644 --- a/chapter/8/big-data.md +++ b/chapter/8/big-data.md @@ -615,9 +615,9 @@ The Hive execution model {% cite thusoo2010hive --file big-data%} composes of th - Optimization: Optimization forms the core of any declarative interface. In the case of Hive, optimization happens through chains of transformation of DAG. A transformation could include even a user defined optimization and it applies an action on the DAG only if a rule is satisfied. Every node in the DAG implements a special interface called as Node interface which makes it easy for the manipulation of the operator DAG using other interfaces like GraphWalker, Dispatcher, Rule, and Processor. Hence, by transformation, we mean walking through a DAG and for every Node we encounter we perform a Rule satisfiability check. If a Rule is satisfied, a corresponding processor is invoked. A Dispatcher maintains a list of Rule to Processor mappings. - <figure class="main-container" align="center"> - <img src="./Hive-transformation.png" alt="Hive transformation" /> - </figure> + <figure class="main-container" align="center"> + <img src="./Hive-transformation.png" alt="Hive transformation" /> + </figure> *Figure to depict the transformation flow during optimization, from:* {%cite thusoo2010hive --file big-data %} |