You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "hongwu (JIRA)" <ji...@apache.org> on 2016/04/10 10:24:25 UTC
[jira] [Resolved] (HAWQ-638) gpload bug using pip installed
PyGreSQL
[ https://issues.apache.org/jira/browse/HAWQ-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
hongwu resolved HAWQ-638.
-------------------------
Resolution: Fixed
> 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)