You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@drill.apache.org by ts...@apache.org on 2015/05/20 08:06:31 UTC

[14/14] drill git commit: escape chars hiding bracketed info > back ticks

escape chars hiding bracketed info > back ticks


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

Branch: refs/heads/gh-pages
Commit: 0120d252a3ec1e8edbb9e01fc7f61c4dc8cae5b5
Parents: 7fb98c5
Author: Kristine Hahn <kh...@maprtech.com>
Authored: Tue May 19 22:58:27 2015 -0700
Committer: Kristine Hahn <kh...@maprtech.com>
Committed: Tue May 19 22:58:27 2015 -0700

----------------------------------------------------------------------
 .../identifying-performance-issues/010-query-plans.md        | 8 ++++----
 .../identifying-performance-issues/020-query-profiles.md     | 6 +++---
 2 files changed, 7 insertions(+), 7 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/drill/blob/0120d252/_docs/performance-tuning/identifying-performance-issues/010-query-plans.md
----------------------------------------------------------------------
diff --git a/_docs/performance-tuning/identifying-performance-issues/010-query-plans.md b/_docs/performance-tuning/identifying-performance-issues/010-query-plans.md
index 7332322..b08435b 100755
--- a/_docs/performance-tuning/identifying-performance-issues/010-query-plans.md
+++ b/_docs/performance-tuning/identifying-performance-issues/010-query-plans.md
@@ -8,7 +8,7 @@ If you experience performance issues in Drill, you can typically identify the so
 
 Drill has an optimizer and a parallelizer that work together to plan a query. Drill creates logical, physical, and execution plans based on the available statistics for an associated set of files or data sources. The number of running Drill nodes and configured runtime settings contribute to how Drill plans and executes a query.
  
-You can use [EXPLAIN commands]({{ site.baseurl }}/docs/explain-commands/) to view the logical and physical plans for a query, however you cannot view the execution plan. To see how Drill executed a query, you can view the query profile in the Drill Web UI at <drill_node_ip_address>:8047.
+You can use [EXPLAIN commands]({{ site.baseurl }}/docs/explain-commands/) to view the logical and physical plans for a query, however you cannot view the execution plan. To see how Drill executed a query, you can view the query profile in the Drill Web UI at `<drill_node_ip_address>:8047`.
 
 ### Logical Plan  
 
@@ -32,7 +32,7 @@ The physical plan shows the major fragments and specific operators with correlat
  
 The physical plan displays the IDs in the following format:
  
-<MajorFragmentID\> - <OperatorID\>
+`<MajorFragmentID> - <OperatorID>`
  
 For example, 00-02 where 00 is the MajorFragmentID and 02 is is the OperatorID.
  
@@ -64,9 +64,9 @@ You can test the performance of a physical plan that Drill generates, modify the
  
 To modify and re-submit a physical plan to Drill, complete the following steps:  
 
-1. Run EXPLAIN PLAN FOR <query\> to see the physical plan for your query.  
+1. Run EXPLAIN PLAN FOR `<query>` to see the physical plan for your query.  
 2. Copy the JSON output of the physical plan, and modify as needed.  
-3. Navigate to the Drill Web UI at <drill\_node\_ip_address\>:8047.  
+3. Navigate to the Drill Web UI at `<drill_node_ip_address>:8047`.  
 4. Select **Query** in the menu bar.  
 ![]({{ site.baseurl }}/docs/img/submit_plan.png)  
 

http://git-wip-us.apache.org/repos/asf/drill/blob/0120d252/_docs/performance-tuning/identifying-performance-issues/020-query-profiles.md
----------------------------------------------------------------------
diff --git a/_docs/performance-tuning/identifying-performance-issues/020-query-profiles.md b/_docs/performance-tuning/identifying-performance-issues/020-query-profiles.md
index a4908f7..badf486 100755
--- a/_docs/performance-tuning/identifying-performance-issues/020-query-profiles.md
+++ b/_docs/performance-tuning/identifying-performance-issues/020-query-profiles.md
@@ -5,7 +5,7 @@ parent: "Identifying Performance Issues"
 
 A profile is a summary of metrics collected for each query that Drill executes. Query profiles provide information that you can use to monitor and analyze query performance. Drill creates a query profile from major, minor, operator, and input stream profiles. Each major fragment profile consists of a list of minor fragment profiles. Each minor fragment profile consists of a list of operator profiles. An operator profile consists of a list of input stream profiles. 
 
-You can view aggregate statistics across profile lists in the Profile tab of the Drill Web UI at <drill\_node\_ip_address\>:8047. You can modify and resubmit queries, or cancel queries. For debugging purposes, you can use profiles in conjunction with Drill logs. See Log and Debug.
+You can view aggregate statistics across profile lists in the Profile tab of the Drill Web UI at `<drill_node_ip_address>:8047`. You can modify and resubmit queries, or cancel queries. For debugging purposes, you can use profiles in conjunction with Drill logs. See Log and Debug.
  
 Metrics in a query profile are associated with a coordinate system of IDs. Drill uses a coordinate system comprised of query, fragment, and operator identifiers to track query execution activities and resources. Drill assigns a unique QueryID to each query received and then assigns IDs to each fragment and operator that executes the query.
  
@@ -19,7 +19,7 @@ Fragment and operator IDs:
 
 ## Viewing a Query Profile  
 
-When you select the Profiles tab in the Drill Web UI at <drill\_node_ip\_address\>:8047, you see a list of the last 100 queries than have run or that are currently running in the cluster.  
+When you select the Profiles tab in the Drill Web UI at `<drill_node_ip_address>:8047`, you see a list of the last 100 queries than have run or that are currently running in the cluster.  
 
 ![]({{ site.baseurl }}/docs/img/list_queries.png)
 
@@ -124,7 +124,7 @@ You may want to cancel a query if it hangs or causes performance bottlenecks. Yo
  
 To cancel a query from the Drill Web UI, complete the following steps:  
 
-1. Navigate to the Drill Web UI at <drill\_node_ip\_address\>:8047.
+1. Navigate to the Drill Web UI at `<drill_node_ip_address>:8047`.
 The Drill node from which you access the Drill Web UI must have an active Drillbit running.
 2. Select Profiles in the toolbar.
 A list of running and completed queries appears.