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

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

GitHub user xunzhang opened a pull request:

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

    HAWQ-638. gpload bugfix using pip installed PyGreSQL

    See https://issues.apache.org/jira/browse/HAWQ-638 for detailed info.

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

    $ git pull https://github.com/xunzhang/incubator-hawq hotfix-gpload

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

    https://github.com/apache/incubator-hawq/pull/567.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 #567
    
----
commit 29a3c439eb8e426d79d3c1e71f37c0d84f3792da
Author: xunzhang <xunzhang...@gmail.com>
Date:   2016-04-07T14:01:59Z

    HAWQ-638. gpload bugfix using pip installed PyGreSQL

----


> gpload bug using pip installed PyGreSQL
> ---------------------------------------
>
>                 Key: HAWQ-638
>                 URL: https://issues.apache.org/jira/browse/HAWQ-638
>             Project: Apache HAWQ
>          Issue Type: Bug
>          Components: Command Line Tools
>            Reporter: hongwu
>            Assignee: Lei Chang
>
> Since greenplum's gpload is based on private patch upon PyGreSQL for internal 
> usage, and gpload.py is copied from greenplum incompletely, it will generate 
> error while using gpload tools.
> Details: 
> self.db.notices() depends on the implementation of pg.DB.notices, which was 
> implemented internal in greenplum, it is wrong to use this attribute in 
> gpload tool of hawq.
> Reference:
> https://github.com/apache/incubator-hawq/blob/master/tools/bin/gpload.py#L704
> https://github.com/greenplum-db/gpdb/blob/master/gpMgmt/bin/pythonSrc/PyGreSQL-4.0/pgmodule.c#L2929



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

Reply via email to