drill-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bridg...@apache.org
Subject [4/4] drill git commit: review comments
Date Tue, 30 Jun 2015 00:34:52 GMT
review comments


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

Branch: refs/heads/gh-pages
Commit: 8587b7f315b6ccb5298fbf69440047430ece2f08
Parents: ef7d3f3
Author: Kristine Hahn <khahn@maprtech.com>
Authored: Mon Jun 29 15:25:20 2015 -0700
Committer: Kristine Hahn <khahn@maprtech.com>
Committed: Mon Jun 29 15:25:20 2015 -0700

----------------------------------------------------------------------
 _docs/110-troubleshooting.md                            | 4 ++--
 _docs/configure-drill/020-configuring-drill-memory.md   | 2 +-
 _docs/sql-reference/sql-commands/030-create-table-as.md | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/drill/blob/8587b7f3/_docs/110-troubleshooting.md
----------------------------------------------------------------------
diff --git a/_docs/110-troubleshooting.md b/_docs/110-troubleshooting.md
index f6f0acc..00edd6f 100755
--- a/_docs/110-troubleshooting.md
+++ b/_docs/110-troubleshooting.md
@@ -54,9 +54,9 @@ If you have any of the following problems, try the suggested solution:
 * [SQLLine Error Starting Drill in Embedded Mode]({{site.baseurl}}/docs/troubleshooting/#sqlline-error-starting-drill-in-embedded-mode)
 
 ### Memory Issues
-Symptom: Memory problems occur when running in-memory operations, such as running queries
that perform window functions.
+Symptom: Memory problems occur when you run certain queries, such as those that perform window
functions.
 
-Solution: The [`planner.memory.max_query_memory_per_node`]({{site.baseurl}}/docs/configuration-options-introduction/#system-options)
system option value determines the Drill limits for running queries, such as window functions,
in memory. When you have a large amount of direct memory allocated, but still encounter memory
issues when running these queries, increase the value of the option.
+Solution: The [`planner.memory.max_query_memory_per_node`]({{site.baseurl}}/docs/configuration-options-introduction/#system-options)
system option value determines the memory limits per node for each running query, especially
for those involving external sorts, such as window functions. When you have a large amount
of direct memory allocated, but still encounter memory issues when running these queries,
increase the value of the option.
 
 ### Query Parsing Errors
 Symptom:  

http://git-wip-us.apache.org/repos/asf/drill/blob/8587b7f3/_docs/configure-drill/020-configuring-drill-memory.md
----------------------------------------------------------------------
diff --git a/_docs/configure-drill/020-configuring-drill-memory.md b/_docs/configure-drill/020-configuring-drill-memory.md
index 100a7c5..d3356e0 100644
--- a/_docs/configure-drill/020-configuring-drill-memory.md
+++ b/_docs/configure-drill/020-configuring-drill-memory.md
@@ -14,7 +14,7 @@ The JVM’s heap memory does not limit the amount of direct memory available
in
 a Drillbit. The on-heap memory for Drill is typically set at 4-8G (default is 4), which should
 suffice because Drill avoids having data sit in heap memory.
 
-The [`planner.memory.max_query_memory_per_node`]({{site.baseurl}}/docs/configuration-options-introduction/#system-options)
system option value determines the Drill limits for running queries, such as window functions,
in memory. When you have a large amount of direct memory allocated, but still encounter memory
issues when running these queries, increase the value of the option.
+The [`planner.memory.max_query_memory_per_node`]({{site.baseurl}}/docs/configuration-options-introduction/#system-options)
system option value determines the memory limits per node for each running query, especially
for those involving external sorts, such as window functions. When you have a large amount
of direct memory allocated, but still encounter memory issues when running these queries,
increase the value of the option.
 
 ## Modifying Drillbit Memory
 

http://git-wip-us.apache.org/repos/asf/drill/blob/8587b7f3/_docs/sql-reference/sql-commands/030-create-table-as.md
----------------------------------------------------------------------
diff --git a/_docs/sql-reference/sql-commands/030-create-table-as.md b/_docs/sql-reference/sql-commands/030-create-table-as.md
index 43bfe68..c5425fd 100644
--- a/_docs/sql-reference/sql-commands/030-create-table-as.md
+++ b/_docs/sql-reference/sql-commands/030-create-table-as.md
@@ -16,7 +16,7 @@ You can use the [PARTITION BY]({{site.baseurl}}/docs/partition-by-clause)
clause
 
 Drill writes files having names, such as 0_0_0.parquet, to the directory named in the CTAS
command or to the workspace that is in use when you run the CTAS statement. You query the
directory as you would query a table.
 
-The following command writes Parquet data from `nation.parquet`, installed with Drill, to
the `/tmp/nation` directory.
+The following command writes Parquet data from `nation.parquet`, installed with Drill, to
the `/tmp/name_key` directory.
 
     USE dfs;
     CREATE TABLE tmp.`name_key` (N_NAME, N_NATIONKEY) AS SELECT N_NATIONKEY, N_NAME FROM
dfs.`/Users/drilluser/apache-drill-1.0/sample-data/nation.parquet`;


Mime
View raw message