[jira] [Assigned] (HAWQ-1073) Remove unused src/backend/libgppc project files

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino reassigned HAWQ-1073:
---

Assignee: Ed Espino  (was: Lei Chang)

> Remove unused src/backend/libgppc project files
> ---
>
> Key: HAWQ-1073
> URL: https://issues.apache.org/jira/browse/HAWQ-1073
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating, 2.0.1.0-incubating
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified Greenplum database legacy files not 
> applicable to HAWQ project.  The files reside in the following location:
> * src/backend/libgppc



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

[jira] [Resolved] (HAWQ-1073) Remove unused src/backend/libgppc project files

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino resolved HAWQ-1073.
-
Resolution: Fixed

Merging complete.

> Remove unused src/backend/libgppc project files
> ---
>
> Key: HAWQ-1073
> URL: https://issues.apache.org/jira/browse/HAWQ-1073
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Ed Espino
>Assignee: Lei Chang
> Fix For: 2.0.0.0-incubating, 2.0.1.0-incubating
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified Greenplum database legacy files not 
> applicable to HAWQ project.  The files reside in the following location:
> * src/backend/libgppc



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

[jira] [Resolved] (HAWQ-1074) General LICENSE cleanup and synchronization with pom.xml

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino resolved HAWQ-1074.
-
Resolution: Fixed

Merging complete.

> General LICENSE cleanup and synchronization with pom.xml
> 
>
> Key: HAWQ-1074
> URL: https://issues.apache.org/jira/browse/HAWQ-1074
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating, 2.0.1.0-incubating
>
> Attachments: rat.txt
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified inconsistencies with LICENSE file.  
> * Moved sections covered by PostgreSQL License to appropriate section
> * Add simplejson license
> * Add PyYAML license
> * Add sha2 license
> * Remove unneeded license files covered by PostgreSQL License
> * Synchronize the component order in LICENSE and pom.xml.  This helps in the 
> IP review.



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

[jira] [Updated] (HAWQ-1073) Remove unused src/backend/libgppc project files

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino updated HAWQ-1073:

Fix Version/s: 2.0.1.0-incubating

> Remove unused src/backend/libgppc project files
> ---
>
> Key: HAWQ-1073
> URL: https://issues.apache.org/jira/browse/HAWQ-1073
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Ed Espino
>Assignee: Lei Chang
> Fix For: 2.0.0.0-incubating, 2.0.1.0-incubating
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified Greenplum database legacy files not 
> applicable to HAWQ project.  The files reside in the following location:
> * src/backend/libgppc



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

[jira] [Resolved] (HAWQ-1072) Remove ASF headers from tools/bin/ext/simplejson and tools/bin/ext/yaml components

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino resolved HAWQ-1072.
-
Resolution: Fixed

Merging complete.

> Remove ASF headers from tools/bin/ext/simplejson and tools/bin/ext/yaml 
> components
> --
>
> Key: HAWQ-1072
> URL: https://issues.apache.org/jira/browse/HAWQ-1072
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating, 2.0.1.0-incubating
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified the Apache License, Version 2.0 
> header was incorrectly placed on the files within the following third party 
> directories:
> * tools/bin/ext/simplejson
> * tools/bin/ext/yaml
> These projects use the MIT license.



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

[jira] [Updated] (HAWQ-1072) Remove ASF headers from tools/bin/ext/simplejson and tools/bin/ext/yaml components

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino updated HAWQ-1072:

Fix Version/s: 2.0.1.0-incubating

> Remove ASF headers from tools/bin/ext/simplejson and tools/bin/ext/yaml 
> components
> --
>
> Key: HAWQ-1072
> URL: https://issues.apache.org/jira/browse/HAWQ-1072
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating, 2.0.1.0-incubating
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified the Apache License, Version 2.0 
> header was incorrectly placed on the files within the following third party 
> directories:
> * tools/bin/ext/simplejson
> * tools/bin/ext/yaml
> These projects use the MIT license.



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

[jira] [Updated] (HAWQ-1074) General LICENSE cleanup and synchronization with pom.xml

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino updated HAWQ-1074:

Fix Version/s: 2.0.1.0-incubating

> General LICENSE cleanup and synchronization with pom.xml
> 
>
> Key: HAWQ-1074
> URL: https://issues.apache.org/jira/browse/HAWQ-1074
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating, 2.0.1.0-incubating
>
> Attachments: rat.txt
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified inconsistencies with LICENSE file.  
> * Moved sections covered by PostgreSQL License to appropriate section
> * Add simplejson license
> * Add PyYAML license
> * Add sha2 license
> * Remove unneeded license files covered by PostgreSQL License
> * Synchronize the component order in LICENSE and pom.xml.  This helps in the 
> IP review.



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

[jira] [Commented] (HAWQ-1072) Remove ASF headers from tools/bin/ext/simplejson and tools/bin/ext/yaml components

[Ed Espino (JIRA)]

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

Ed Espino commented on HAWQ-1072:
-

Pushed to Apache HAWQ 2.0.0.0-incubating release branch.

> Remove ASF headers from tools/bin/ext/simplejson and tools/bin/ext/yaml 
> components
> --
>
> Key: HAWQ-1072
> URL: https://issues.apache.org/jira/browse/HAWQ-1072
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified the Apache License, Version 2.0 
> header was incorrectly placed on the files within the following third party 
> directories:
> * tools/bin/ext/simplejson
> * tools/bin/ext/yaml
> These projects use the MIT license.



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

[jira] [Commented] (HAWQ-1073) Remove unused src/backend/libgppc project files

[Ed Espino (JIRA)]

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

Ed Espino commented on HAWQ-1073:
-

Pushed to Apache HAWQ 2.0.0.0-incubating release branch.

> Remove unused src/backend/libgppc project files
> ---
>
> Key: HAWQ-1073
> URL: https://issues.apache.org/jira/browse/HAWQ-1073
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Ed Espino
>Assignee: Lei Chang
> Fix For: 2.0.0.0-incubating
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified Greenplum database legacy files not 
> applicable to HAWQ project.  The files reside in the following location:
> * src/backend/libgppc



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

[jira] [Commented] (HAWQ-1074) General LICENSE cleanup and synchronization with pom.xml

[Ed Espino (JIRA)]

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

Ed Espino commented on HAWQ-1074:
-

Pushed to Apache HAWQ 2.0.0.0-incubating release branch.

> General LICENSE cleanup and synchronization with pom.xml
> 
>
> Key: HAWQ-1074
> URL: https://issues.apache.org/jira/browse/HAWQ-1074
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating
>
> Attachments: rat.txt
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified inconsistencies with LICENSE file.  
> * Moved sections covered by PostgreSQL License to appropriate section
> * Add simplejson license
> * Add PyYAML license
> * Add sha2 license
> * Remove unneeded license files covered by PostgreSQL License
> * Synchronize the component order in LICENSE and pom.xml.  This helps in the 
> IP review.



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

[jira] [Updated] (HAWQ-1074) General LICENSE cleanup and synchronization with pom.xml

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino updated HAWQ-1074:

Attachment: rat.txt

Here is the passing header for Apache HAWQ 2.0.0.0-incubator release rat report:

{code}
*
Summary
---
Generated at: 2016-09-23T21:53:05-07:00
Notes: 4
Binaries: 0
Archives: 1
Standards: 2893

Apache Licensed: 2061
Generated Documents: 0

JavaDocs are generated and so license header is optional
Generated files do not required license headers

0 Unknown Licenses

***

Unapproved licenses:


***
{code}

> General LICENSE cleanup and synchronization with pom.xml
> 
>
> Key: HAWQ-1074
> URL: https://issues.apache.org/jira/browse/HAWQ-1074
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating
>
> Attachments: rat.txt
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified inconsistencies with LICENSE file.  
> * Moved sections covered by PostgreSQL License to appropriate section
> * Add simplejson license
> * Add PyYAML license
> * Add sha2 license
> * Remove unneeded license files covered by PostgreSQL License
> * Synchronize the component order in LICENSE and pom.xml.  This helps in the 
> IP review.



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

[jira] [Updated] (HAWQ-1074) General LICENSE cleanup and synchronization with pom.xml

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino updated HAWQ-1074:

Description: 
During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
mentor Roman Shaposhnik), we identified inconsistencies with LICENSE file.  
* Moved sections covered by PostgreSQL License to appropriate section
* Add simplejson license
* Add PyYAML license
* Add sha2 license
* Remove unneeded license files covered by PostgreSQL License
* Synchronize the component order in LICENSE and pom.xml.  This helps in the IP 
review.

  was:
During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
mentor Roman Shaposhnik), we identified inconsistencies with LICENSE file.  
* Moved sections covered by PostgreSQL License to appropriate section
* Add simplejson
* Add PyYAML
* Remove unneeded license files covered by PostgreSQL License
* Synchronize the component order in LICENSE and pom.xml.  This helps in the IP 
review.


> General LICENSE cleanup and synchronization with pom.xml
> 
>
> Key: HAWQ-1074
> URL: https://issues.apache.org/jira/browse/HAWQ-1074
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified inconsistencies with LICENSE file.  
> * Moved sections covered by PostgreSQL License to appropriate section
> * Add simplejson license
> * Add PyYAML license
> * Add sha2 license
> * Remove unneeded license files covered by PostgreSQL License
> * Synchronize the component order in LICENSE and pom.xml.  This helps in the 
> IP review.



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

[jira] [Commented] (HAWQ-1046) Document migration of LibHDFS3 library to HAWQ

[Roman Shaposhnik (JIRA)]

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

Roman Shaposhnik commented on HAWQ-1046:


[~bolke] first of all lets address the proverbial elephant in the room -- if 
we're talking about long-term viable community efforts around C/C++ direct 
interface with HDFS than there's HADOOP-10388. The ultimate effort really can't 
be separated from the Apache Hadoop community. I don't think it would be fair 
to assume that what we do for HAWQ is somehow a replacement for that. In fact, 
long term, I really see the two efforts merging. See HDFS-6994 for example.

Thus, having yet another project on GitHub seems counter-productive.

> Document migration of LibHDFS3 library to HAWQ
> --
>
> Key: HAWQ-1046
> URL: https://issues.apache.org/jira/browse/HAWQ-1046
> Project: Apache HAWQ
>  Issue Type: Wish
>  Components: libhdfs
>Reporter: Matthew Rocklin
>Assignee: hongwu
> Fix For: backlog
>
>
> Some people used to depend on the libhdfs3 library maintained alongside HAWQ. 
>  This library was merged into the HAWQ codebase, making the situation a bit 
> more confusing.
> Is independent use of libhdfs3 still supported by this community?  If so what 
> is the best way for packagers to reason about versions and releases of this 
> component?  It would be convenient to see documentation on how people can 
> best depend on libhdfs3 separately from HAWQ if this is an intention.
> It looks like people have actually submitted work to the old version
> See: https://github.com/Pivotal-Data-Attic/pivotalrd-libhdfs3/pull/28
> It looks like the warning that the library had moved has been removed:
> https://github.com/Pivotal-Data-Attic/pivotalrd-libhdfs3/commit/ddcb2404a5a67e0f39fe49ed20591545c48ff426
> This removal may lead to some frustration



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

[GitHub] incubator-hawq issue #896: [#126526845] Port recent changes from gpdb for ha...

[huor]

Github user huor commented on the issue:

https://github.com/apache/incubator-hawq/pull/896
  
@oarap thanks for the update. @liming01 and @paul-guo-, please review the 
port.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #935: HAWQ-1055. Fix to handle decimal with prec...

[shivzone]

GitHub user shivzone opened a pull request:

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

HAWQ-1055. Fix to handle decimal with precision,scale



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

$ git pull https://github.com/shivzone/incubator-hawq HAWQ-1055

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

https://github.com/apache/incubator-hawq/pull/935.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 #935


commit 03e2190f7d00eebff0af4735ba00b838bfc9f4a4
Author: Shivram Mani 
Date:   2016-09-23T21:51:05Z

HAWQ-1055. Fix to handle decimal with precision,scale




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Assigned] (HAWQ-1074) General LICENSE cleanup and synchronization with pom.xml

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino reassigned HAWQ-1074:
---

Assignee: Ed Espino  (was: Lei Chang)

> General LICENSE cleanup and synchronization with pom.xml
> 
>
> Key: HAWQ-1074
> URL: https://issues.apache.org/jira/browse/HAWQ-1074
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified inconsistencies with LICENSE file.  
> * Moved sections covered by PostgreSQL License to appropriate section
> * Add simplejson
> * Add PyYAML
> * Remove unneeded license files covered by PostgreSQL License
> * Synchronize the component order in LICENSE and pom.xml.  This helps in the 
> IP review.



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

[jira] [Created] (HAWQ-1073) Remove unused src/backend/libgppc project files

[Ed Espino (JIRA)]

Ed Espino created HAWQ-1073:
---

 Summary: Remove unused src/backend/libgppc project files
 Key: HAWQ-1073
 URL: https://issues.apache.org/jira/browse/HAWQ-1073
 Project: Apache HAWQ
  Issue Type: Bug
Reporter: Ed Espino
Assignee: Lei Chang
 Fix For: 2.0.0.0-incubating


During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
mentor Roman Shaposhnik), we identified Greenplum database legacy files not 
applicable to HAWQ project.  The files reside in the following location:

* src/backend/libgppc



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

[jira] [Assigned] (HAWQ-1072) Remove ASF headers from tools/bin/ext/simplejson and tools/bin/ext/yaml components

[Ed Espino (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ed Espino reassigned HAWQ-1072:
---

Assignee: Ed Espino  (was: Lei Chang)

> Remove ASF headers from tools/bin/ext/simplejson and tools/bin/ext/yaml 
> components
> --
>
> Key: HAWQ-1072
> URL: https://issues.apache.org/jira/browse/HAWQ-1072
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Build
>Reporter: Ed Espino
>Assignee: Ed Espino
> Fix For: 2.0.0.0-incubating
>
>
> During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
> mentor Roman Shaposhnik), we identified the Apache License, Version 2.0 
> header was incorrectly placed on the files within the following third party 
> directories:
> * tools/bin/ext/simplejson
> * tools/bin/ext/yaml
> These projects use the MIT license.



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

[jira] [Created] (HAWQ-1072) Remove ASF headers from tools/bin/ext/simplejson and tools/bin/ext/yaml components

[Ed Espino (JIRA)]

Ed Espino created HAWQ-1072:
---

 Summary: Remove ASF headers from tools/bin/ext/simplejson and 
tools/bin/ext/yaml components
 Key: HAWQ-1072
 URL: https://issues.apache.org/jira/browse/HAWQ-1072
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Build
Reporter: Ed Espino
Assignee: Lei Chang
 Fix For: 2.0.0.0-incubating


During the Apache HAWQ 2.0.0.0-incubator review (guided by Apache project 
mentor Roman Shaposhnik), we identified the Apache License, Version 2.0 header 
was incorrectly placed on the files within the following third party 
directories:

* tools/bin/ext/simplejson
* tools/bin/ext/yaml

These projects use the MIT license.



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

[jira] [Comment Edited] (HAWQ-1055) Fractional part is being dropped for decimal/numeric column with no modifiers in HiveORC profile

[Shivram Mani (JIRA)]

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

Shivram Mani edited comment on HAWQ-1055 at 9/23/16 8:52 PM:
-

The following table shows how Hive decimal fields will be handled in HAWQ:

|| HAWQ Type || Hive Type || Behavior |
| numeric(precision, scale) | decimal(precision,scale) | As long as HAWQ has a 
higher scale/precision than defined in Hive, would be fine. If precision/scale 
is lower in HAWQ compared to Hive, will be reported as an error  |
| numeric(precision) | decimal(precision) | Hawq and Hive restricts scale to 0 |
| numeric | decimal | Hive defaults to <38,18> while HAWQ permits upto max 
(131072) for precision and upto 16383 for scale |


was (Author: shivram):
The following table shows how Hive decimal fields will be handled in HAWQ:

|| HAWQ Type || Hive Type || Behavior |
| numeric(precision, scale) | decimal(precision,scale) | As long as HAWQ has a 
higher scale/precision than defined in Hive, would be fine. If precision/scale 
is lower in HAWQ compared to Hive, will be reported as an error  |
| numeric(precision) | decimal(precision) | Hawq and Hive restricts scale to 0 |
| numeric | decimal | Hive defaults to <38,38> while HAWQ permits upto max 
(131072) for precision and upto 16383 for scale |

> Fractional part is being dropped for decimal/numeric column with no modifiers 
> in HiveORC profile
> 
>
> Key: HAWQ-1055
> URL: https://issues.apache.org/jira/browse/HAWQ-1055
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Oleksandr Diachenko
>Assignee: Shivram Mani
>Priority: Critical
> Fix For: 2.0.1.0-incubating
>
>




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

[jira] [Comment Edited] (HAWQ-1055) Fractional part is being dropped for decimal/numeric column with no modifiers in HiveORC profile

[Shivram Mani (JIRA)]

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

Shivram Mani edited comment on HAWQ-1055 at 9/23/16 8:52 PM:
-

If HAWQ doesn't define precision,scale info for the column, we will assume 
<38,18> as that is the maximum permitted value in Hive


was (Author: shivram):
If HAWQ doesn't define precision,scale info for the column, we will assume 
<38,38> as that is the maximum permitted value in Hive

> Fractional part is being dropped for decimal/numeric column with no modifiers 
> in HiveORC profile
> 
>
> Key: HAWQ-1055
> URL: https://issues.apache.org/jira/browse/HAWQ-1055
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Oleksandr Diachenko
>Assignee: Shivram Mani
>Priority: Critical
> Fix For: 2.0.1.0-incubating
>
>




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

[jira] [Updated] (HAWQ-1071) add PXF HiveText and HiveRC profile examples to the documentation

[Lisa Owen (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lisa Owen updated HAWQ-1071:

Priority: Minor  (was: Major)

> add PXF HiveText and HiveRC profile examples to the documentation
> -
>
> Key: HAWQ-1071
> URL: https://issues.apache.org/jira/browse/HAWQ-1071
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: Documentation
>Reporter: Lisa Owen
>Assignee: David Yozie
>Priority: Minor
> Fix For: 2.0.1.0-incubating
>
>
> the current PXF Hive documentation includes an example for only the Hive 
> profile.  add examples for HiveText and HiveRC profiles.



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

[jira] [Created] (HAWQ-1071) add PXF HiveText and HiveRC profile examples to the documentation

[Lisa Owen (JIRA)]

Lisa Owen created HAWQ-1071:
---

 Summary: add PXF HiveText and HiveRC profile examples to the 
documentation
 Key: HAWQ-1071
 URL: https://issues.apache.org/jira/browse/HAWQ-1071
 Project: Apache HAWQ
  Issue Type: Improvement
  Components: Documentation
Reporter: Lisa Owen
Assignee: David Yozie
 Fix For: 2.0.1.0-incubating


the current PXF Hive documentation includes an example for only the Hive 
profile.  add examples for HiveText and HiveRC profiles.



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

[GitHub] incubator-hawq pull request #914: HAWQ-1045. RPM updates for side by side in...

[shivzone]

Github user shivzone commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/914#discussion_r80308625
  
--- Diff: pxf/pxf-service/src/scripts/pxf-service ---
@@ -22,8 +22,8 @@
 
 pxf_root=/usr/lib/pxf
 env_script=/etc/pxf/conf/pxf-env.sh
-tomcat_root=/opt/pivotal/apache-tomcat
-tomcat_templates=/opt/pivotal/pxf/tomcat-templates
+tomcat_root=/opt/apache-tomcat
+tomcat_templates=/opt/pxf/tomcat-templates
--- End diff --

Same holds true even for the library and conf paths as well being 
referenced in the classpath file (using their symlinks). Should be fine, as the 
expectation is that pxf would be installed using the virtual rpm


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #914: HAWQ-1045. RPM updates for side by side in...

[denalex]

Github user denalex commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/914#discussion_r80301161
  
--- Diff: pxf/build.gradle ---
@@ -283,6 +287,28 @@ project('pxf-service') {
 }
 }
 
+project('pxf') {
+jar.enabled = false
+ospackage {
+summary = 'HAWQ Extension Framework (PXF)'
+description = 'HAWQ Extension framework Virtual RPM'
+packager = ' '
+packageGroup = 'Development/Libraries'
+release = buildNumber() + '.' + project.osFamily
+buildHost = ' '
+
+requires(versionedPackageName('pxf-hdfs'), project.version, 
GREATER | EQUAL)
+requires(versionedPackageName('pxf-hive'), project.version, 
GREATER | EQUAL)
+requires(versionedPackageName('pxf-hbase'), project.version, 
GREATER | EQUAL)
+requires(versionedPackageName('pxf-json'), project.version, 
GREATER | EQUAL)
+
+link('/usr/lib/pxf', "/usr/lib/pxf-${project.version}")
+link('/etc/pxf', "pxf-${project.version}")
--- End diff --

no full path for "pxf-${project.version}" ?


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #914: HAWQ-1045. RPM updates for side by side in...

[shivzone]

Github user shivzone commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/914#discussion_r80299815
  
--- Diff: pxf/build.gradle ---
@@ -283,6 +287,25 @@ project('pxf-service') {
 }
 }
 
+project('pxf') {
--- End diff --

done


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #914: HAWQ-1045. RPM updates for side by side in...

[shivzone]

Github user shivzone commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/914#discussion_r80293126
  
--- Diff: pxf/settings.gradle ---
@@ -19,9 +19,10 @@
 
 rootProject.name = 'pxf'
 
+include 'pxf'
--- End diff --

settings.gradle must have every project included. Without which we would 
get the following error: Project with path 'pxf-service' could not be found in 
root project 'pxf'.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (HAWQ-1029) hawq register --help information not correct

[hongwu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/HAWQ-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

hongwu updated HAWQ-1029:
-
Affects Version/s: 2.0.1.0-incubating

> hawq register --help information not correct
> 
>
> Key: HAWQ-1029
> URL: https://issues.apache.org/jira/browse/HAWQ-1029
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Command Line Tools
>Affects Versions: 2.0.1.0-incubating
>Reporter: Lili Ma
>Assignee: hongwu
> Fix For: 2.0.1.0-incubating
>
>
> The example for usage case 1 is not correct, should modify it.
> $ hawq register postgres parquet_table hdfs://localhost:8020/temp/hive.paq



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

[GitHub] incubator-hawq issue #934: HAWQ-1061. Fix register with empty folder in usag...

[linwen]

Github user linwen commented on the issue:

https://github.com/apache/incubator-hawq/pull/934
  
+1 


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq issue #934: HAWQ-1061. Fix register with empty folder in usag...

[wengyanqing]

Github user wengyanqing commented on the issue:

https://github.com/apache/incubator-hawq/pull/934
  
+1


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq issue #934: HAWQ-1061. Fix register with empty folder in usag...

[ictmalili]

Github user ictmalili commented on the issue:

https://github.com/apache/incubator-hawq/pull/934
  
LGTM. +1


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #883: HAWQ-1029. Update hawqregister_help info.

[ictmalili]

Github user ictmalili commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/883#discussion_r80217715
  
--- Diff: tools/doc/hawqregister_help ---
@@ -37,10 +35,19 @@ The file(s) to be registered and the table in HAWQ must 
be in the
 same HDFS cluster.
 
 Use Case2:
-User should be able to use hawq register to register table files into a 
new HAWQ cluster.
-It is some kind of protecting against corruption from users' perspective.
-Users use the last-known-good metadata to update the portion of catalog 
managing HDFS blocks.
-The table files or dictionary should be backuped(such as using distcp) 
into the same path in the new HDFS setting.
+Hawq register can register both AO and parquet format table, and the files 
to be registered are listed in the .yml configuration file.
+This configuration file can be generated by hawq extract. Register through 
.yml configuration doesn’t require the table already exist,
+since .yml file contains table schema already.
+HAWQ register behaviors differently with different options: 
+ * If the table does not exist, hawq register will create table and do 
register. 
+ * If table already exist, hawq register will append the files to the 
existing table.
+ * If --force option specified, hawq register will erase existing catalog 
+   table pg_aoseg.pg_aoseg_$relid/pg_aoseg.pg_paqseg_$relid data for the 
table and 
+   re-register according to .yml configuration file definition. Note. If 
there are
+   files under table directory which are not specified in .yml 
configuration file, it will throw error out.
+Note. Without --force specified, if some file specified in .yml 
configuration file lie under the table directory, hawq register will throw 
error out.
+Note. With --force option specified, if there are files under table 
directory which are not specified in .yml configuration file, hawq register 
will throw error out.
+Note. For both the use cases of hawq register, if the table is hash 
distributed, hawq register just check the file number to be registered has to 
be integral multiple multiple times of this table’s bucket number, and check 
whether the distribution key specified in .yml configuration file is same as 
that of table. It does not check whether files are actually distributed by the 
key.
--- End diff --

Use Case 1 does not support hash distributed table register. 


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #883: HAWQ-1029. Update hawqregister_help info.

[ictmalili]

Github user ictmalili commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/883#discussion_r80218098
  
--- Diff: tools/doc/hawqregister_help ---
@@ -37,10 +35,19 @@ The file(s) to be registered and the table in HAWQ must 
be in the
 same HDFS cluster.
 
 Use Case2:
-User should be able to use hawq register to register table files into a 
new HAWQ cluster.
-It is some kind of protecting against corruption from users' perspective.
-Users use the last-known-good metadata to update the portion of catalog 
managing HDFS blocks.
-The table files or dictionary should be backuped(such as using distcp) 
into the same path in the new HDFS setting.
+Hawq register can register both AO and parquet format table, and the files 
to be registered are listed in the .yml configuration file.
+This configuration file can be generated by hawq extract. Register through 
.yml configuration doesn’t require the table already exist,
+since .yml file contains table schema already.
+HAWQ register behaviors differently with different options: 
+ * If the table does not exist, hawq register will create table and do 
register. 
+ * If table already exist, hawq register will append the files to the 
existing table.
+ * If --force option specified, hawq register will erase existing catalog 
+   table pg_aoseg.pg_aoseg_$relid/pg_aoseg.pg_paqseg_$relid data for the 
table and 
+   re-register according to .yml configuration file definition. Note. If 
there are
+   files under table directory which are not specified in .yml 
configuration file, it will throw error out.
+Note. Without --force specified, if some file specified in .yml 
configuration file lie under the table directory, hawq register will throw 
error out.
+Note. With --force option specified, if there are files under table 
directory which are not specified in .yml configuration file, hawq register 
will throw error out.
+Note. For both the use cases of hawq register, if the table is hash 
distributed, hawq register just check the file number to be registered has to 
be integral multiple multiple times of this table’s bucket number, and check 
whether the distribution key specified in .yml configuration file is same as 
that of table. It does not check whether files are actually distributed by the 
key.
--- End diff --

We 


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #883: HAWQ-1029. Update hawqregister_help info.

[ictmalili]

Github user ictmalili commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/883#discussion_r80217825
  
--- Diff: tools/doc/hawqregister_help ---
@@ -37,10 +35,19 @@ The file(s) to be registered and the table in HAWQ must 
be in the
 same HDFS cluster.
 
 Use Case2:
-User should be able to use hawq register to register table files into a 
new HAWQ cluster.
-It is some kind of protecting against corruption from users' perspective.
-Users use the last-known-good metadata to update the portion of catalog 
managing HDFS blocks.
-The table files or dictionary should be backuped(such as using distcp) 
into the same path in the new HDFS setting.
+Hawq register can register both AO and parquet format table, and the files 
to be registered are listed in the .yml configuration file.
+This configuration file can be generated by hawq extract. Register through 
.yml configuration doesn’t require the table already exist,
+since .yml file contains table schema already.
+HAWQ register behaviors differently with different options: 
+ * If the table does not exist, hawq register will create table and do 
register. 
+ * If table already exist, hawq register will append the files to the 
existing table.
+ * If --force option specified, hawq register will erase existing catalog 
+   table pg_aoseg.pg_aoseg_$relid/pg_aoseg.pg_paqseg_$relid data for the 
table and 
+   re-register according to .yml configuration file definition. Note. If 
there are
+   files under table directory which are not specified in .yml 
configuration file, it will throw error out.
+Note. Without --force specified, if some file specified in .yml 
configuration file lie under the table directory, hawq register will throw 
error out.
+Note. With --force option specified, if there are files under table 
directory which are not specified in .yml configuration file, hawq register 
will throw error out.
+Note. For both the use cases of hawq register, if the table is hash 
distributed, hawq register just check the file number to be registered has to 
be integral multiple multiple times of this table’s bucket number, and check 
whether the distribution key specified in .yml configuration file is same as 
that of table. It does not check whether files are actually distributed by the 
key.
--- End diff --

"hawq register just check the file number to be registered has to be 
integral multiple multiple times of this table’s bucket number"  There are 
many useless words there. "integral" and "multiple"


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #883: HAWQ-1029. Update hawqregister_help info.

[ictmalili]

Github user ictmalili commented on a diff in the pull request:

https://github.com/apache/incubator-hawq/pull/883#discussion_r80218089
  
--- Diff: tools/doc/hawqregister_help ---
@@ -110,14 +113,24 @@ table 'pg_aoseg.pg_paqseg_77160'.
 *
 EXAMPLE FOR USAGE2
 *
-$ psql -c "drop table if exists table;"
-$ psql -c "create table table(i int) with (appendonly=true, 
orientation=parquet) distributed by (i);"
-$ psql -c "insert into table values(1), (2), (3);"
-$ hawq extract -d postgres -o t.yml table
-$ hawq register -d postgres -c t.yml newtable
-In this example, suppose that "table" is a table in old HAWQ Cluster, user 
dump "t.yml" yaml file to
-save the metadata of "table". To register the "newtable" in a new HAWQ 
Cluster, user run "hawq register"
-to register the newtable with the given yaml file "t.yml".
+This example shows hawq register functionality of hawq register according 
to yml configuration file.
+Usually the yml configuration file is generated by hawq extract.
+This example shows the life cycle of hawq extract and hawq register.
+
+Firstly, create a table and insert some data into it:
+$ psql -c "create table paq1(a int, b varchar(10))with(appendonly=true, 
orientation=parquet);"
+$ psql -c "insert into paq1 values(generate_series(1,1000), 'abcde');"
+
+Secondly, extract the table metadata information out:
+$ hawq extract -o paq1.yml paq1
+
+Thirdly, register to new table paq2 identifying yml file:
+$ hawq register --config paq1.yml paq2
+
+Finally, select the new table to look at whether the content has already 
been registered.
+$ select count(*) from paq2;
+
+In the above example, the final result must be return 1000.
--- End diff --

change "must be" to "should"


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq issue #883: HAWQ-1029. Update hawqregister_help info.

[xunzhang]

Github user xunzhang commented on the issue:

https://github.com/apache/incubator-hawq/pull/883
  
cc @ictmalili @linwen again


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq issue #934: HAWQ-1061. Fix register with empty folder in usag...

[xunzhang]

Github user xunzhang commented on the issue:

https://github.com/apache/incubator-hawq/pull/934
  
cc @ictmalili @stanlyxiang 


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #934: HAWQ-1061. Fix register with empty folder ...

[xunzhang]

GitHub user xunzhang opened a pull request:

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

HAWQ-1061. Fix register with empty folder in usage1.



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

$ git pull https://github.com/xunzhang/incubator-hawq HAWQ-1061

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

https://github.com/apache/incubator-hawq/pull/934.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 #934






---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #933: HAWQ-991. Support registering hash distrib...

[xunzhang]

Github user xunzhang closed the pull request at:

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


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq issue #933: HAWQ-991. Support registering hash distribution t...

[xunzhang]

Github user xunzhang commented on the issue:

https://github.com/apache/incubator-hawq/pull/933
  
Merged into master.


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq issue #933: HAWQ-991. Support registering hash distribution t...

[stanlyxiang]

Github user stanlyxiang commented on the issue:

https://github.com/apache/incubator-hawq/pull/933
  
+1


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq issue #933: HAWQ-991. Support registering hash distribution t...

[xunzhang]

Github user xunzhang commented on the issue:

https://github.com/apache/incubator-hawq/pull/933
  
cc @ictmalili @stanlyxiang 


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #933: HAWQ-991. Support registering hash distrib...

[xunzhang]

GitHub user xunzhang opened a pull request:

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

HAWQ-991. Support registering hash distribution table into random 
distribution table.



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

$ git pull https://github.com/xunzhang/incubator-hawq HAWQ-991

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

https://github.com/apache/incubator-hawq/pull/933.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 #933


commit 9f9d9882d5a1751bc91ef9c9d4110c17cca921d9
Author: xunzhang 
Date:   2016-09-23T07:49:20Z

HAWQ-991. Support registering hash distribution table into random 
distribution table.




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-hawq pull request #932: HAWQ-1024. Add rollback before all necessa...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---