diff options
| author | msabhi <abhi.is2006@gmail.com> | 2016-12-12 12:41:38 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-12-12 12:41:38 -0500 |
| commit | c2e14a66591f5fa7c878515d5841e3c75ccc9bc5 (patch) | |
| tree | ac1aaa4a32c41328a941c32d91075ee5f7de2134 /chapter | |
| parent | 2384fa2339950af6a25715c4825a6680611f5a16 (diff) | |
Update big-data.md
Diffstat (limited to 'chapter')
| -rw-r--r-- | chapter/8/big-data.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/chapter/8/big-data.md b/chapter/8/big-data.md index 345bde3..f3055b0 100644 --- a/chapter/8/big-data.md +++ b/chapter/8/big-data.md @@ -391,10 +391,11 @@ The Hive execution model composes of the below important components (and as show Execution Engine : Execution Engine finally executes the tasks in order of their dependencies. A MapReduce task first serializes its part of the plan into a plan.xml file. This file is then added to the job cache and mappers and reducers are spawned to execute relevant sections of the operator DAG. The final results are stored to a temporary location and then moved to the final destination (in the case of say INSERT INTO query). + <figure class="main-container"> <img src="./Hive-architecture.png" alt="Hive architecture" /> </figure> - +*Hive architecture diagram* Summarizing the flow - the query is first submitted via CLI/web UI/any other interface. The query undergoes all the compiler phases as explained above to form an optimized DAG of MapReduce and hdfs tasks which the execution engine executes in its correct order using Hadoop. |