Repository: drill
Updated Branches:
  refs/heads/gh-pages ccd89314c -> c7e28e75e


fix release from 1.13 to 1.14 for hash join spill support


Project: http://git-wip-us.apache.org/repos/asf/drill/repo
Commit: http://git-wip-us.apache.org/repos/asf/drill/commit/c7e28e75
Tree: http://git-wip-us.apache.org/repos/asf/drill/tree/c7e28e75
Diff: http://git-wip-us.apache.org/repos/asf/drill/diff/c7e28e75

Branch: refs/heads/gh-pages
Commit: c7e28e75e2977ad43f2dac818e3f2612533b07c2
Parents: ccd8931
Author: Bridget Bevens <bbev...@maprtech.com>
Authored: Tue Mar 13 18:21:09 2018 -0700
Committer: Bridget Bevens <bbev...@maprtech.com>
Committed: Tue Mar 13 18:21:09 2018 -0700

----------------------------------------------------------------------
 ...050-sort-based-and-hash-based-memory-constrained-operators.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/drill/blob/c7e28e75/_docs/performance-tuning/query-plans-and-tuning/050-sort-based-and-hash-based-memory-constrained-operators.md
----------------------------------------------------------------------
diff --git 
a/_docs/performance-tuning/query-plans-and-tuning/050-sort-based-and-hash-based-memory-constrained-operators.md
 
b/_docs/performance-tuning/query-plans-and-tuning/050-sort-based-and-hash-based-memory-constrained-operators.md
index 315150c..3e5b305 100644
--- 
a/_docs/performance-tuning/query-plans-and-tuning/050-sort-based-and-hash-based-memory-constrained-operators.md
+++ 
b/_docs/performance-tuning/query-plans-and-tuning/050-sort-based-and-hash-based-memory-constrained-operators.md
@@ -1,6 +1,6 @@
 ---
 title: "Sort-Based and Hash-Based Memory-Constrained Operators"
-date: 2018-03-14 00:58:06 UTC
+date: 2018-03-14 01:21:10 UTC
 parent: "Query Plans and Tuning"
 --- 
 
@@ -19,7 +19,7 @@ When the Sort, Hash Aggregate, and Hash Join operators finish 
processing the dat
 
 Ideally, you want to allocate enough memory for Drill to perform all 
operations in memory. When data spills to disk, you will not see any difference 
in terms of how queries run, however spilling to disk can impact performance 
due to the additional I/O required to write data to disk and read the data 
back. See Memory Allocation (page 4) for more information. 
 
-**Note:** Drill 1.13 and later supports spilling to disk for the Hash Join, 
Hash Aggregate, and Sort operators. Drill 1.11 and 1.12 supports spilling to 
disk for the Hash Aggregate and Sort operators. Releases of Drill prior to 1.11 
only support spilling to disk for the Sort operator.  
+**Note:** Drill 1.14 and later supports spilling to disk for the Hash Join, 
Hash Aggregate, and Sort operators. Drill 1.11 and 1.12 supports spilling to 
disk for the Hash Aggregate and Sort operators. Releases of Drill prior to 1.11 
only support spilling to disk for the Sort operator.  
 
 **Spill Locations** 
 

Reply via email to