You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by blrunner <gi...@git.apache.org> on 2016/01/22 08:38:26 UTC

[GitHub] tajo pull request: TAJO-2061: Add description for EXPLAIN statemen...

GitHub user blrunner opened a pull request:

    https://github.com/apache/tajo/pull/947

    TAJO-2061: Add description for EXPLAIN statement.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/blrunner/tajo TAJO-2061

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/tajo/pull/947.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #947
    
----
commit 66071b14dd5e77514589c37e3446c84b0d294ff8
Author: JaeHwa Jung <bl...@apache.org>
Date:   2016-01-22T07:37:31Z

    TAJO-2061: Add description for EXPLAIN statement.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] tajo pull request: TAJO-2061: Add description for EXPLAIN statemen...

Posted by jinossy <gi...@git.apache.org>.
Github user jinossy commented on the pull request:

    https://github.com/apache/tajo/pull/947#issuecomment-173859389
  
    +1 LGTM!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] tajo pull request: TAJO-2061: Add description for EXPLAIN statemen...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/tajo/pull/947


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] tajo pull request: TAJO-2061: Add description for EXPLAIN statemen...

Posted by blrunner <gi...@git.apache.org>.
Github user blrunner commented on the pull request:

    https://github.com/apache/tajo/pull/947#issuecomment-173858385
  
    Thanks @jinossy . I rebased your comments.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] tajo pull request: TAJO-2061: Add description for EXPLAIN statemen...

Posted by jinossy <gi...@git.apache.org>.
Github user jinossy commented on a diff in the pull request:

    https://github.com/apache/tajo/pull/947#discussion_r50515287
  
    --- Diff: tajo-docs/src/main/sphinx/sql_language/explain.rst ---
    @@ -0,0 +1,93 @@
    +************************
    +EXPLAIN
    +************************
    +
    +*Synopsis*
    +
    +.. code-block:: sql
    +
    +  EXPLAIN [GLOBAL] statement
    +
    +
    +*Description*
    +
    +Show the logical or distributed execution plan of a statement.
    +
    +
    +*Examples*
    +
    +Logical plan:
    +
    +.. code-block:: sql
    +
    +  default> EXPLAIN SELECT l_orderkey, count(*) FROM lineitem GROUP BY l_orderkey;
    +  explain
    +  -------------------------------
    +  GROUP_BY(1)(l_orderkey)
    +    => exprs: (count())
    +    => target list: default.lineitem.l_orderkey (INT8), ?count (INT8)
    +    => out schema:{(2) default.lineitem.l_orderkey (INT8), ?count (INT8)}
    +    => in schema:{(1) default.lineitem.l_orderkey (INT8)}
    +     SCAN(0) on default.lineitem
    +       => target list: default.lineitem.l_orderkey (INT8)
    +       => out schema: {(1) default.lineitem.l_orderkey (INT8)}
    +       => in schema: {(16) default.lineitem.l_orderkey (INT8), default.lineitem.l_partkey (INT8), default.lineitem.l_suppkey (INT8), default.lineitem.l_linenumber (INT8), default.lineitem.l_quantity (FLOAT8), default.lineitem.l_extendedprice (FLOAT8), default.lineitem.l_discount (FLOAT8), default.lineitem.l_tax (FLOAT8), default.lineitem.l_returnflag (TEXT), default.lineitem.l_linestatus (TEXT), default.lineitem.l_shipdate (DATE), default.lineitem.l_commitdate (DATE), default.lineitem.l_receiptdate (DATE), default.lineitem.l_shipinstruct (TEXT), default.lineitem.l_shipmode (TEXT), default.lineitem.l_comment (TEXT)}
    +
    +
    +Distributed plan:
    --- End diff --
    
    How about global plan?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---