You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/18 21:59:20 UTC

[jira] [Commented] (HAWQ-934) Populate canSetTag of PlannedStmt from Query object

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

ASF GitHub Bot commented on HAWQ-934:
-------------------------------------

GitHub user hsyuan opened a pull request:

    https://github.com/apache/incubator-hawq/pull/799

    HAWQ-934. Populate canSetTag of PlannedStmt from Query object

    HAWQ generated an error if a single query resulted in multiple query plans because of rule transformation and the plans were produced by PQO. This is because of an incorrect directive in the plan to lock the same resource more than once. This issue has been fixed.

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

    $ git pull https://github.com/hsyuan/incubator-hawq HAWQ-934

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

    https://github.com/apache/incubator-hawq/pull/799.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 #799
    
----
commit 8ccca05f62a0a8e315fa21799d5401a792470477
Author: Haisheng Yuan and Lubomir Petrov <hy...@pivotal.io>
Date:   2016-07-18T21:51:39Z

    HAWQ-934. Populate canSetTag of PlannedStmt from Query object

----


> Populate canSetTag of PlannedStmt from Query object
> ---------------------------------------------------
>
>                 Key: HAWQ-934
>                 URL: https://issues.apache.org/jira/browse/HAWQ-934
>             Project: Apache HAWQ
>          Issue Type: Bug
>          Components: Optimizer
>            Reporter: Haisheng Yuan
>            Assignee: Venkatesh
>             Fix For: 2.0.1.0-incubating
>
>
> HAWQ generated an error if a single query resulted in multiple query plans because of rule transformation and the plans were produced by PQO. This is because of an incorrect directive in the plan to lock the same resource more than once.



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