You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/08/26 16:55:45 UTC

[jira] [Commented] (TAJO-1801) Table name is not unique of tableDescMap in QueryMasterTask

    [ https://issues.apache.org/jira/browse/TAJO-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14713597#comment-14713597 ] 

ASF GitHub Bot commented on TAJO-1801:
--------------------------------------

GitHub user jihoonson opened a pull request:

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

    TAJO-1801: Table name is not unique of tableDescMap in QueryMasterTask

    

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

    $ git pull https://github.com/jihoonson/tajo-2 TAJO-1801

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

    https://github.com/apache/tajo/pull/710.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 #710
    
----
commit 01db4334775b3095385df6efc42d30591eafa443
Author: Jihoon Son <ji...@apache.org>
Date:   2015-08-25T13:43:18Z

    TAJO-1801

commit 42ba6e72b48aa0c54f2eadb25f9e08dde2351da0
Author: Jihoon Son <ji...@apache.org>
Date:   2015-08-26T14:49:04Z

    Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/tajo into TAJO-1801

commit 972e93c788b0928073d76ce55cc48e4d51c00d32
Author: Jihoon Son <ji...@apache.org>
Date:   2015-08-26T14:54:05Z

    TAJO-1801

----


> Table name is not unique of tableDescMap in QueryMasterTask
> -----------------------------------------------------------
>
>                 Key: TAJO-1801
>                 URL: https://issues.apache.org/jira/browse/TAJO-1801
>             Project: Tajo
>          Issue Type: Bug
>          Components: QueryMaster
>            Reporter: Jihoon Son
>            Assignee: Jihoon Son
>            Priority: Critical
>             Fix For: 0.11.0
>
>
> See the title.
> Query planner and optimizer can make a wrong decision due to this bug.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)