date:20160401

[jira] [Created] (HAWQ-622) fix libhdfs3 readme

2016-04-01 Thread Lei Chang (JIRA)

Lei Chang created HAWQ-622:
--

 Summary: fix libhdfs3 readme
 Key: HAWQ-622
 URL: https://issues.apache.org/jira/browse/HAWQ-622
 Project: Apache HAWQ
  Issue Type: Bug
  Components: libhdfs
Reporter: Lei Chang
Assignee: Lei Chang


==
Libhdfs3 is developed by Pivotal and used in HAWQ, which
is a massive parallel database engine in Pivotal Hadoop
Distribution.
==






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

[jira] [Resolved] (HAWQ-608) libyarn hot refactor

2016-04-01 Thread hongwu (JIRA)


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

hongwu resolved HAWQ-608.
-
Resolution: Fixed

> libyarn hot refactor
> 
>
> Key: HAWQ-608
> URL: https://issues.apache.org/jira/browse/HAWQ-608
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: libyarn
>Reporter: hongwu
>Assignee: Lei Chang
>
> I built libyarn under Ubuntu12.04 with gcc(4.7) and got `rethrow_if_nested is 
> ambiguous to the compiler` building error. 
> The bug results from the the name of inside defined function 
> rethrow_if_nested conflict with std::rethrow_if_nested and code in libyarn 
> use `using namespace std;`, it is terrible...



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

[jira] [Closed] (HAWQ-410) Incorporate libhdfs3 into HAWQ source tree as direct source dep.

2016-04-01 Thread Lei Chang (JIRA)


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

Lei Chang closed HAWQ-410.
--
Resolution: Fixed

> Incorporate libhdfs3 into HAWQ source tree as direct source dep.
> 
>
> Key: HAWQ-410
> URL: https://issues.apache.org/jira/browse/HAWQ-410
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Affects Versions: 2.0.0-beta-incubating
>Reporter: Konstantin Boudnik
>Assignee: Lei Chang
>Priority: Blocker
> Fix For: 2.0.0-beta-incubating
>
>
> This project even has the component for libhdfs, so I don't see why the 
> source code of what seems to be a mandatory dependency be hosted elsewhere. 
> Let's add this into the source tree before the release. The motivations are 
> discussed [here|http://is.gd/MZUN49]



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

[jira] [Commented] (HAWQ-410) Incorporate libhdfs3 into HAWQ source tree as direct source dep.

2016-04-01 Thread Lei Chang (JIRA)


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

Lei Chang commented on HAWQ-410:


The code is in. Let's close this.

> Incorporate libhdfs3 into HAWQ source tree as direct source dep.
> 
>
> Key: HAWQ-410
> URL: https://issues.apache.org/jira/browse/HAWQ-410
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Affects Versions: 2.0.0-beta-incubating
>Reporter: Konstantin Boudnik
>Assignee: Lei Chang
>Priority: Blocker
> Fix For: 2.0.0-beta-incubating
>
>
> This project even has the component for libhdfs, so I don't see why the 
> source code of what seems to be a mandatory dependency be hosted elsewhere. 
> Let's add this into the source tree before the release. The motivations are 
> discussed [here|http://is.gd/MZUN49]



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

[jira] [Closed] (HAWQ-618) Import libhdfs3 for internal management

2016-04-01 Thread Lei Chang (JIRA)


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

Lei Chang closed HAWQ-618.
--
Resolution: Duplicate

> Import libhdfs3 for internal management
> ---
>
> Key: HAWQ-618
> URL: https://issues.apache.org/jira/browse/HAWQ-618
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Reporter: hongwu
>Assignee: Lei Chang
>
> Import libhdfs3 for internal update, similar with libyarn package inside HAWQ 
> project.



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

[jira] [Commented] (HAWQ-410) Incorporate libhdfs3 into HAWQ source tree as direct source dep.

2016-04-01 Thread Lei Chang (JIRA)


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

Lei Chang commented on HAWQ-410:


Looks we forgot the jira has been started due to the duplicate tracking with 
tracker stories in pivotal. Let's combine the two JIRAs together.

> Incorporate libhdfs3 into HAWQ source tree as direct source dep.
> 
>
> Key: HAWQ-410
> URL: https://issues.apache.org/jira/browse/HAWQ-410
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Affects Versions: 2.0.0-beta-incubating
>Reporter: Konstantin Boudnik
>Assignee: Lei Chang
>Priority: Blocker
> Fix For: 2.0.0-beta-incubating
>
>
> This project even has the component for libhdfs, so I don't see why the 
> source code of what seems to be a mandatory dependency be hosted elsewhere. 
> Let's add this into the source tree before the release. The motivations are 
> discussed [here|http://is.gd/MZUN49]



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

[jira] [Comment Edited] (HAWQ-615) PXF getMetadata endpoint fails if set of items described by passed pattern have unsupported by Hawq Hive objects

2016-04-01 Thread Goden Yao (JIRA)


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

Goden Yao edited comment on HAWQ-615 at 4/1/16 10:45 PM:
-

A preferable behavior is: (IMHO)

1) if query for a single table that contains complex types we don't support 
yet, gracefully error out with messages like "the table contains complex types 
which is not supported"

2) if query with a pattern, we should return the tables that only contain types 
we support and also a list of table names we don't support. Alternatively, we 
can just put error tables in the log and only return good tables.


was (Author: godenyao):
A preferable behavior is: (IMHO)

1) if query for a single table that contains complex types we don't support 
yet, gracefully error out with messages like "the table contains complex types 
which is not supported"

2) if query with a pattern, we should return the tables that only contain types 
we support and also a list of table names we don't support.

> PXF getMetadata endpoint fails if set of items described by passed pattern 
> have unsupported by Hawq Hive objects
> 
>
> Key: HAWQ-615
> URL: https://issues.apache.org/jira/browse/HAWQ-615
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Hcatalog, PXF
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
> Fix For: 2.0.0
>
>
> STR:
> 1) Hive instance having at least one view object
> 2) Read metadata from PXF using wildcard as a pattern: 
> http://localhost:51200/pxf/v14/Metadata/getMetadata?profile=hive=*
> AR:
> {code}
> java.lang.UnsupportedOperationException: Hive views are not supported by HAWQ
>   
> org.apache.hawq.pxf.plugins.hive.utilities.HiveUtilities.getHiveTable(HiveUtilities.java:79)
>   
> org.apache.hawq.pxf.plugins.hive.HiveMetadataFetcher.getMetadata(HiveMetadataFetcher.java:67)
>   
> org.apache.hawq.pxf.service.rest.MetadataResource.read(MetadataResource.java:107)
>   sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)
>   
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   java.lang.reflect.Method.invoke(Method.java:606)
>   
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>   
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
>   
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
>   
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
>   
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
>   
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
>   
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
>   
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
>   
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>   org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> {code}
> ER:
> Response should contain set of items which are supported.



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

[jira] [Comment Edited] (HAWQ-410) Incorporate libhdfs3 into HAWQ source tree as direct source dep.

2016-04-01 Thread Goden Yao (JIRA)


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

Goden Yao edited comment on HAWQ-410 at 4/1/16 10:35 PM:
-

[~lei_chang] - is the new JIRA (HAWQ-618) addressing this JIRA's concern? 
Please comment. Thanks!


was (Author: godenyao):
@Lei - is the new JIRA (HAWQ-618) addressing this JIRA's concern? Please 
comment. Thanks!

> Incorporate libhdfs3 into HAWQ source tree as direct source dep.
> 
>
> Key: HAWQ-410
> URL: https://issues.apache.org/jira/browse/HAWQ-410
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Affects Versions: 2.0.0-beta-incubating
>Reporter: Konstantin Boudnik
>Assignee: Lei Chang
>Priority: Blocker
> Fix For: 2.0.0-beta-incubating
>
>
> This project even has the component for libhdfs, so I don't see why the 
> source code of what seems to be a mandatory dependency be hosted elsewhere. 
> Let's add this into the source tree before the release. The motivations are 
> discussed [here|http://is.gd/MZUN49]



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

[jira] [Commented] (HAWQ-615) PXF getMetadata endpoint fails if set of items described by passed pattern have unsupported by Hawq Hive objects

2016-04-01 Thread Goden Yao (JIRA)


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

Goden Yao commented on HAWQ-615:


A preferable behavior is: (IMHO)

1) if query for a single table that contains complex types we don't support 
yet, gracefully error out with messages like "the table contains complex types 
which is not supported"

2) if query with a pattern, we should return the tables that only contain types 
we support and also a list of table names we don't support.

> PXF getMetadata endpoint fails if set of items described by passed pattern 
> have unsupported by Hawq Hive objects
> 
>
> Key: HAWQ-615
> URL: https://issues.apache.org/jira/browse/HAWQ-615
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Hcatalog, PXF
>Reporter: Oleksandr Diachenko
>Assignee: Oleksandr Diachenko
> Fix For: 2.0.0
>
>
> STR:
> 1) Hive instance having at least one view object
> 2) Read metadata from PXF using wildcard as a pattern: 
> http://localhost:51200/pxf/v14/Metadata/getMetadata?profile=hive=*
> AR:
> {code}
> java.lang.UnsupportedOperationException: Hive views are not supported by HAWQ
>   
> org.apache.hawq.pxf.plugins.hive.utilities.HiveUtilities.getHiveTable(HiveUtilities.java:79)
>   
> org.apache.hawq.pxf.plugins.hive.HiveMetadataFetcher.getMetadata(HiveMetadataFetcher.java:67)
>   
> org.apache.hawq.pxf.service.rest.MetadataResource.read(MetadataResource.java:107)
>   sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)
>   
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   java.lang.reflect.Method.invoke(Method.java:606)
>   
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
>   
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
>   
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
>   
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
>   
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   
> com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
>   
> com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
>   
> com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
>   
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1469)
>   
> com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1400)
>   
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1349)
>   
> com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1339)
>   
> com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
>   
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:537)
>   
> com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:699)
>   javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
>   org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
> {code}
> ER:
> Response should contain set of items which are supported.



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

[jira] [Comment Edited] (HAWQ-410) Incorporate libhdfs3 into HAWQ source tree as direct source dep.

2016-04-01 Thread Goden Yao (JIRA)


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

Goden Yao edited comment on HAWQ-410 at 4/1/16 10:34 PM:
-

@Lei - is the new JIRA (HAWQ-618) addressing this JIRA's concern? Please 
comment. Thanks!


was (Author: godenyao):
@Lei - is the new JIRA addressing this JIRA's concern? Please comment. Thanks!

> Incorporate libhdfs3 into HAWQ source tree as direct source dep.
> 
>
> Key: HAWQ-410
> URL: https://issues.apache.org/jira/browse/HAWQ-410
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Affects Versions: 2.0.0-beta-incubating
>Reporter: Konstantin Boudnik
>Assignee: Lei Chang
>Priority: Blocker
> Fix For: 2.0.0-beta-incubating
>
>
> This project even has the component for libhdfs, so I don't see why the 
> source code of what seems to be a mandatory dependency be hosted elsewhere. 
> Let's add this into the source tree before the release. The motivations are 
> discussed [here|http://is.gd/MZUN49]



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

[jira] [Commented] (HAWQ-410) Incorporate libhdfs3 into HAWQ source tree as direct source dep.

2016-04-01 Thread Goden Yao (JIRA)


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

Goden Yao commented on HAWQ-410:


@Lei - is the new JIRA addressing this JIRA's concern? Please comment. Thanks!

> Incorporate libhdfs3 into HAWQ source tree as direct source dep.
> 
>
> Key: HAWQ-410
> URL: https://issues.apache.org/jira/browse/HAWQ-410
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Affects Versions: 2.0.0-beta-incubating
>Reporter: Konstantin Boudnik
>Assignee: Lei Chang
>Priority: Blocker
> Fix For: 2.0.0-beta-incubating
>
>
> This project even has the component for libhdfs, so I don't see why the 
> source code of what seems to be a mandatory dependency be hosted elsewhere. 
> Let's add this into the source tree before the release. The motivations are 
> discussed [here|http://is.gd/MZUN49]



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

[jira] [Commented] (HAWQ-621) TupleDescriptor leak during split_partition

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-621:
-

GitHub user foyzur opened a pull request:

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

HAWQ-621. Fixing tuple descriptor leak in split_rows during an ALTER TABLE 
SPLIT PARTITION. 

During split_rows, we may create new tuple table slot inside 
reconstructMatchingTupleSlot() if the descriptor of the new target relation 
does not match the source relation. We then cache this slot inside the target 
relation's ri_resultSlot. This process pins the tuple descriptor of the new 
target relation. However, at the end of split_rows, when we are finished with 
this "cached" tuple table slot, we don't free them. This results in a WARNING 
that we leaked a tuple descriptor.


Solution:
---

Following the call path of split_rows, the method split_rows() is only 
called from 

```
split_rows(Relation, Relation, Relation) : void
ATPExecPartSplit(Relation *, AlterPartitionCmd *) : void
ATExecCmd(List * *, AlteredTableInfo *, Relation *, 
AlterTableCmd *) : void
ATPExecPartAlter(List * *, AlteredTableInfo *, 
Relation, AlterPartitionCmd *) : void
ATRewriteCatalogs(List * *) : void
```

By the time we call split_rows, we know precisely the two relation where we 
will be inserting into. We create ResultRelInfo for both of these relations 
(the two target relations) at the beginning of split_rows(), called rria, and 
rrib. Both of these ResultRelInfo only have lifespan of the containing method 
split_rows(). We use the ri_resultSlot of these two rria and rrib to cache the 
TupleTableSlot inside reconstructMatchingTupleSlot() where we create additional 
TupleTableSlot using the tuple descriptors of the two target relations, 
therefore pinning these two target relation's TupleDesc. As the rria and rrib 
only live during split_rows() and only used for all the tuples in ONE CALL of 
split_rows(), we can easily drop the additional TupleTableSlot ri_resultSlot of 
both rria and rrib, and that will also unpin underlying TupleDesc.

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

$ git pull https://github.com/foyzur/incubator-hawq tupledesc

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

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


commit 88085577d226efb60b4c1e8ecdec6187816c8f1e
Author: Foyzur Rahman 
Date:   2016-03-22T01:11:13Z

HAWQ-621. Fixing tuple descriptor leak in split_rows during an ALTER TABLE 
SPLIT PARTITION.




> TupleDescriptor leak during split_partition
> ---
>
> Key: HAWQ-621
> URL: https://issues.apache.org/jira/browse/HAWQ-621
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Query Execution
>Reporter: Foyzur Rahman
>Assignee: George Caragea
>
> During split_rows, we may create new tuple table slot inside 
> reconstructMatchingTupleSlot() if the descriptor of the new target relation 
> does not match the source relation. We then cache this slot inside the target 
> relation's ri_resultSlot. This process pins the tuple descriptor of the new 
> target relation. However, at the end of split_rows, when we are finished with 
> this "cached" tuple table slot, we don't free them. This results in a WARNING 
> that we leaked a tuple descriptor.
> Repro:
> {code}
> -- Test for tuple descriptor leak during row splitting
> DROP TABLE IF EXISTS split_tupdesc_leak;
> CREATE TABLE split_tupdesc_leak
> (
>ym character varying(6) NOT NULL,
>suid character varying(50) NOT NULL,
>genre_ids character varying(20)[]
> ) 
> WITH (APPENDONLY=true, ORIENTATION=row, COMPRESSTYPE=zlib, OIDS=FALSE)
> DISTRIBUTED BY (suid)
> PARTITION BY LIST(ym)
> (
>   DEFAULT PARTITION p_split_tupdesc_leak_ym  WITH (appendonly=true, 
> orientation=row, compresstype=zlib)
> );
> INSERT INTO split_tupdesc_leak VALUES 
> ('201412','0001EC1TPEvT5SaJKIR5yYXlFQ7tS','{0}');
> ALTER TABLE split_tupdesc_leak SPLIT DEFAULT PARTITION AT ('201412')
>   INTO (PARTITION p_split_tupdesc_leak_ym, PARTITION 
> p_split_tupdesc_leak_ym_201412);
> DROP TABLE split_tupdesc_leak;
> {code}



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

[jira] [Created] (HAWQ-621) TupleDescriptor leak during split_partition

2016-04-01 Thread Foyzur Rahman (JIRA)

Foyzur Rahman created HAWQ-621:
--

 Summary: TupleDescriptor leak during split_partition
 Key: HAWQ-621
 URL: https://issues.apache.org/jira/browse/HAWQ-621
 Project: Apache HAWQ
  Issue Type: Bug
  Components: Query Execution
Reporter: Foyzur Rahman
Assignee: George Caragea


During split_rows, we may create new tuple table slot inside 
reconstructMatchingTupleSlot() if the descriptor of the new target relation 
does not match the source relation. We then cache this slot inside the target 
relation's ri_resultSlot. This process pins the tuple descriptor of the new 
target relation. However, at the end of split_rows, when we are finished with 
this "cached" tuple table slot, we don't free them. This results in a WARNING 
that we leaked a tuple descriptor.

Repro:

{code}
-- Test for tuple descriptor leak during row splitting
DROP TABLE IF EXISTS split_tupdesc_leak;
CREATE TABLE split_tupdesc_leak
(
   ym character varying(6) NOT NULL,
   suid character varying(50) NOT NULL,
   genre_ids character varying(20)[]
) 
WITH (APPENDONLY=true, ORIENTATION=row, COMPRESSTYPE=zlib, OIDS=FALSE)
DISTRIBUTED BY (suid)
PARTITION BY LIST(ym)
(
DEFAULT PARTITION p_split_tupdesc_leak_ym  WITH (appendonly=true, 
orientation=row, compresstype=zlib)
);

INSERT INTO split_tupdesc_leak VALUES 
('201412','0001EC1TPEvT5SaJKIR5yYXlFQ7tS','{0}');

ALTER TABLE split_tupdesc_leak SPLIT DEFAULT PARTITION AT ('201412')
INTO (PARTITION p_split_tupdesc_leak_ym, PARTITION 
p_split_tupdesc_leak_ym_201412);

DROP TABLE split_tupdesc_leak;
{code}




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

[jira] [Commented] (HAWQ-617) Add a flag to hawq config to allow skipping hosts on which ssh fails and continue with syncing configurations files

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-617:
-

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

https://github.com/apache/incubator-hawq/pull/546#discussion_r58235606
  
--- Diff: .gitignore ---
@@ -1,54 +1 @@
-# Object files
--- End diff --

will delete it, not needed.


> Add a flag to hawq config to allow skipping hosts on which ssh fails and 
> continue with syncing configurations files
> ---
>
> Key: HAWQ-617
> URL: https://issues.apache.org/jira/browse/HAWQ-617
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: bhuvnesh chaudhary
>Assignee: Lei Chang
>
> Add a flag to hawq config to allow skipping hosts on which ssh fails and 
> continue with syncing configurations files.
> Currently, if there is any one bad host, sync operations fails. Hawq activate 
> standby uses hawq config to update hawq-site.xml configuration, however if 
> the active master host is down, it fails.



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

[jira] [Resolved] (HAWQ-620) Remove useless codes in resourcebroker_NONE.c

2016-04-01 Thread Lin Wen (JIRA)


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

Lin Wen resolved HAWQ-620.
--
Resolution: Fixed

> Remove useless codes in resourcebroker_NONE.c
> -
>
> Key: HAWQ-620
> URL: https://issues.apache.org/jira/browse/HAWQ-620
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Lin Wen
>Assignee: Lin Wen
>




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

[jira] [Commented] (HAWQ-620) Remove useless codes in resourcebroker_NONE.c

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-620:
-

Github user linwen closed the pull request at:

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


> Remove useless codes in resourcebroker_NONE.c
> -
>
> Key: HAWQ-620
> URL: https://issues.apache.org/jira/browse/HAWQ-620
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Lin Wen
>Assignee: Lin Wen
>




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

[jira] [Commented] (HAWQ-620) Remove useless codes in resourcebroker_NONE.c

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-620:
-

Github user jiny2 commented on the pull request:

https://github.com/apache/incubator-hawq/pull/548#issuecomment-204355747
  
+1


> Remove useless codes in resourcebroker_NONE.c
> -
>
> Key: HAWQ-620
> URL: https://issues.apache.org/jira/browse/HAWQ-620
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Lin Wen
>Assignee: Lin Wen
>




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

[jira] [Commented] (HAWQ-620) Remove useless codes in resourcebroker_NONE.c

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-620:
-

Github user yaoj2 commented on the pull request:

https://github.com/apache/incubator-hawq/pull/548#issuecomment-204331315
  
+1


> Remove useless codes in resourcebroker_NONE.c
> -
>
> Key: HAWQ-620
> URL: https://issues.apache.org/jira/browse/HAWQ-620
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Lin Wen
>Assignee: Lin Wen
>




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

[jira] [Commented] (HAWQ-620) Remove useless codes in resourcebroker_NONE.c

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-620:
-

GitHub user linwen opened a pull request:

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

HAWQ-620. remove useless codes in resourcebroker_NONE.c

Please review, thanks! 

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

$ git pull https://github.com/linwen/incubator-hawq hawq-620

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

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


commit af4ad99dd7c15c55e403a583bcb49647dce2317e
Author: Wen Lin 
Date:   2016-04-01T09:38:21Z

HAWQ-620. remove useless codes in resourcebroker_NONE.c




> Remove useless codes in resourcebroker_NONE.c
> -
>
> Key: HAWQ-620
> URL: https://issues.apache.org/jira/browse/HAWQ-620
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Lin Wen
>Assignee: Lin Wen
>




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

[jira] [Commented] (HAWQ-618) Import libhdfs3 for internal management

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-618:
-

Github user asfgit closed the pull request at:

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


> Import libhdfs3 for internal management
> ---
>
> Key: HAWQ-618
> URL: https://issues.apache.org/jira/browse/HAWQ-618
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Reporter: hongwu
>Assignee: Lei Chang
>
> Import libhdfs3 for internal update, similar with libyarn package inside HAWQ 
> project.



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

[jira] [Assigned] (HAWQ-620) Remove useless codes in resourcebroker_NONE.c

2016-04-01 Thread Lin Wen (JIRA)


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

Lin Wen reassigned HAWQ-620:


Assignee: Lin Wen  (was: Lei Chang)

> Remove useless codes in resourcebroker_NONE.c
> -
>
> Key: HAWQ-620
> URL: https://issues.apache.org/jira/browse/HAWQ-620
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Lin Wen
>Assignee: Lin Wen
>




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

[jira] [Commented] (HAWQ-618) Import libhdfs3 for internal management

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-618:
-

Github user liming01 commented on the pull request:

https://github.com/apache/incubator-hawq/pull/547#issuecomment-204328141
  
+1.


> Import libhdfs3 for internal management
> ---
>
> Key: HAWQ-618
> URL: https://issues.apache.org/jira/browse/HAWQ-618
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Reporter: hongwu
>Assignee: Lei Chang
>
> Import libhdfs3 for internal update, similar with libyarn package inside HAWQ 
> project.



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

[jira] [Commented] (HAWQ-618) Import libhdfs3 for internal management

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-618:
-

Github user changleicn commented on the pull request:

https://github.com/apache/incubator-hawq/pull/547#issuecomment-204327491
  
LGTM


> Import libhdfs3 for internal management
> ---
>
> Key: HAWQ-618
> URL: https://issues.apache.org/jira/browse/HAWQ-618
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Reporter: hongwu
>Assignee: Lei Chang
>
> Import libhdfs3 for internal update, similar with libyarn package inside HAWQ 
> project.



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

[jira] [Updated] (HAWQ-614) Table with Segment Reject Limit fails to flush AO file when all data is rejected

2016-04-01 Thread Lei Chang (JIRA)


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

Lei Chang updated HAWQ-614:
---
Assignee: hongwu  (was: Lei Chang)

> Table with Segment Reject Limit fails to flush AO file when all data is 
> rejected
> 
>
> Key: HAWQ-614
> URL: https://issues.apache.org/jira/browse/HAWQ-614
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: External Tables
>Reporter: Kyle R Dunn
>Assignee: hongwu
>Priority: Minor
> Attachments: image008.jpg
>
>
> An error message (attached) is received if *all* data gets rejected (for any 
> reason) when using segment reject limit option with an error table.



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

[jira] [Commented] (HAWQ-618) Import libhdfs3 for internal management

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-618:
-

Github user xunzhang commented on the pull request:

https://github.com/apache/incubator-hawq/pull/547#issuecomment-204320833
  
cc @changleicn 


> Import libhdfs3 for internal management
> ---
>
> Key: HAWQ-618
> URL: https://issues.apache.org/jira/browse/HAWQ-618
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Reporter: hongwu
>Assignee: Lei Chang
>
> Import libhdfs3 for internal update, similar with libyarn package inside HAWQ 
> project.



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

[jira] [Commented] (HAWQ-617) Add a flag to hawq config to allow skipping hosts on which ssh fails and continue with syncing configurations files

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-617:
-

Github user radarwave commented on the pull request:

https://github.com/apache/incubator-hawq/pull/546#issuecomment-204319977
  
How about pass this option to hawq stop/start cluster?


> Add a flag to hawq config to allow skipping hosts on which ssh fails and 
> continue with syncing configurations files
> ---
>
> Key: HAWQ-617
> URL: https://issues.apache.org/jira/browse/HAWQ-617
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: bhuvnesh chaudhary
>Assignee: Lei Chang
>
> Add a flag to hawq config to allow skipping hosts on which ssh fails and 
> continue with syncing configurations files.
> Currently, if there is any one bad host, sync operations fails. Hawq activate 
> standby uses hawq config to update hawq-site.xml configuration, however if 
> the active master host is down, it fails.



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

[jira] [Commented] (HAWQ-618) Import libhdfs3 for internal management

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-618:
-

GitHub user xunzhang opened a pull request:

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

HAWQ-618. Import libhdfs3 library for internal management & LICENSE 
modified.



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

$ git pull https://github.com/xunzhang/incubator-hawq libhdfs3-import

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

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


commit bc0904ab02bb3e8c3e3596ce139b3ea6b52e2685
Author: xunzhang 
Date:   2016-04-01T08:59:27Z

HAWQ-618. Import libhdfs3 library for internal management and LICENSE 
modified




> Import libhdfs3 for internal management
> ---
>
> Key: HAWQ-618
> URL: https://issues.apache.org/jira/browse/HAWQ-618
> Project: Apache HAWQ
>  Issue Type: Improvement
>  Components: libhdfs
>Reporter: hongwu
>Assignee: Lei Chang
>
> Import libhdfs3 for internal update, similar with libyarn package inside HAWQ 
> project.



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

[jira] [Commented] (HAWQ-307) Ubuntu Support

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-307:
-

Github user changleicn commented on the pull request:

https://github.com/apache/incubator-hawq/pull/250#issuecomment-204311853
  
nice


> Ubuntu Support
> --
>
> Key: HAWQ-307
> URL: https://issues.apache.org/jira/browse/HAWQ-307
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Build
>Reporter: Lei Chang
>Assignee: Clay B.
> Fix For: 2.1.0
>
>
> To support HAWQ running on Ubuntu OS 14.04.3



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

[jira] [Created] (HAWQ-619) Change 'gpextract' to 'hawqextract' for InputFormat unit test

2016-04-01 Thread Chunling Wang (JIRA)

Chunling Wang created HAWQ-619:
--

 Summary: Change 'gpextract' to 'hawqextract' for InputFormat unit 
test
 Key: HAWQ-619
 URL: https://issues.apache.org/jira/browse/HAWQ-619
 Project: Apache HAWQ
  Issue Type: Task
  Components: Tests
Reporter: Chunling Wang
Assignee: Jiali Yao


Change 'gpextract' to 'hawqextract' in SimpleTableLocalTester.java for 
InputFormat unit test.



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

[jira] [Created] (HAWQ-618) Import libhdfs3 for internal management

2016-04-01 Thread hongwu (JIRA)

hongwu created HAWQ-618:
---

 Summary: Import libhdfs3 for internal management
 Key: HAWQ-618
 URL: https://issues.apache.org/jira/browse/HAWQ-618
 Project: Apache HAWQ
  Issue Type: Improvement
  Components: libhdfs
Reporter: hongwu
Assignee: Lei Chang


Import libhdfs3 for internal update, similar with libyarn package inside HAWQ 
project.



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

[jira] [Commented] (HAWQ-307) Ubuntu Support

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-307:
-

Github user xunzhang commented on the pull request:

https://github.com/apache/incubator-hawq/pull/250#issuecomment-204298198
  
@changleicn , this pull request seems good except the above python problem, 
I have tested this patch under Ubuntu12.04/Mac OSX together with the upstream. 
We could merge this into master after he fixed that problem.


> Ubuntu Support
> --
>
> Key: HAWQ-307
> URL: https://issues.apache.org/jira/browse/HAWQ-307
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Build
>Reporter: Lei Chang
>Assignee: Clay B.
> Fix For: 2.1.0
>
>
> To support HAWQ running on Ubuntu OS 14.04.3



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

[jira] [Commented] (HAWQ-307) Ubuntu Support

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-307:
-

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

https://github.com/apache/incubator-hawq/pull/250#discussion_r58172195
  
--- Diff: tools/bin/gppylib/commands/unix.py ---
@@ -925,7 +925,7 @@ def getDescendentProcesses(pid):
 children = list()
 grandchildren = list()
 
-for p in psi.process.ProcessTable().values():
+for p in psutil.process.ProcessTable().values():
--- End diff --

@cbaenziger This usage here is wrong since `psutil` module has no attribute 
`process`. Why should you use `psutil` in stead of `psi`?


> Ubuntu Support
> --
>
> Key: HAWQ-307
> URL: https://issues.apache.org/jira/browse/HAWQ-307
> Project: Apache HAWQ
>  Issue Type: New Feature
>  Components: Build
>Reporter: Lei Chang
>Assignee: Clay B.
> Fix For: 2.1.0
>
>
> To support HAWQ running on Ubuntu OS 14.04.3



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

[jira] [Commented] (HAWQ-617) Add a flag to hawq config to allow skipping hosts on which ssh fails and continue with syncing configurations files

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-617:
-

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

https://github.com/apache/incubator-hawq/pull/546#discussion_r58170586
  
--- Diff: .gitignore ---
@@ -1,54 +1 @@
-# Object files
--- End diff --

Why changing to .gitignore file?


> Add a flag to hawq config to allow skipping hosts on which ssh fails and 
> continue with syncing configurations files
> ---
>
> Key: HAWQ-617
> URL: https://issues.apache.org/jira/browse/HAWQ-617
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: bhuvnesh chaudhary
>Assignee: Lei Chang
>
> Add a flag to hawq config to allow skipping hosts on which ssh fails and 
> continue with syncing configurations files.
> Currently, if there is any one bad host, sync operations fails. Hawq activate 
> standby uses hawq config to update hawq-site.xml configuration, however if 
> the active master host is down, it fails.



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

[jira] [Commented] (HAWQ-608) libyarn hot refactor

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-608:
-

Github user xunzhang commented on the pull request:

https://github.com/apache/incubator-hawq/pull/534#issuecomment-204271018
  
@linwen , thanks for merging, I will close this pull request.


> libyarn hot refactor
> 
>
> Key: HAWQ-608
> URL: https://issues.apache.org/jira/browse/HAWQ-608
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: libyarn
>Reporter: hongwu
>Assignee: Lei Chang
>
> I built libyarn under Ubuntu12.04 with gcc(4.7) and got `rethrow_if_nested is 
> ambiguous to the compiler` building error. 
> The bug results from the the name of inside defined function 
> rethrow_if_nested conflict with std::rethrow_if_nested and code in libyarn 
> use `using namespace std;`, it is terrible...



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

[jira] [Commented] (HAWQ-608) libyarn hot refactor

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-608:
-

Github user xunzhang closed the pull request at:

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


> libyarn hot refactor
> 
>
> Key: HAWQ-608
> URL: https://issues.apache.org/jira/browse/HAWQ-608
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: libyarn
>Reporter: hongwu
>Assignee: Lei Chang
>
> I built libyarn under Ubuntu12.04 with gcc(4.7) and got `rethrow_if_nested is 
> ambiguous to the compiler` building error. 
> The bug results from the the name of inside defined function 
> rethrow_if_nested conflict with std::rethrow_if_nested and code in libyarn 
> use `using namespace std;`, it is terrible...



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

[jira] [Commented] (HAWQ-617) Add a flag to hawq config to allow skipping hosts on which ssh fails and continue with syncing configurations files

2016-04-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on HAWQ-617:
-

GitHub user bhuvnesh2703 opened a pull request:

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

HAWQ-617 Add option to skip syncing configuration files

Currently Activate standby operations uses 'hawq config' to update 
hawq-site.xml. However, in case any of the HAWQ host is down, the operation 
fails while syncing up the configuration. In case of big clusters, there can be 
few segment hosts which are down and that will prohibit activating standby.
Thus, introduced a new flag in hawq config to ignore bad hosts and continue 
syncing files on hosts on which test ssh is successful

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

$ git pull https://github.com/apache/incubator-hawq HAWQ-617

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

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


commit 7e8331a7e314c9d5b7f2ec65078fa069271a284d
Author: Bhuvnesh Chaudhary 
Date:   2016-04-01T06:14:54Z

[#116576425] - Add option to ignore hosts on which SSH test fails to skip 
syncing configuration files




> Add a flag to hawq config to allow skipping hosts on which ssh fails and 
> continue with syncing configurations files
> ---
>
> Key: HAWQ-617
> URL: https://issues.apache.org/jira/browse/HAWQ-617
> Project: Apache HAWQ
>  Issue Type: Bug
>Reporter: bhuvnesh chaudhary
>Assignee: Lei Chang
>
> Add a flag to hawq config to allow skipping hosts on which ssh fails and 
> continue with syncing configurations files.
> Currently, if there is any one bad host, sync operations fails. Hawq activate 
> standby uses hawq config to update hawq-site.xml configuration, however if 
> the active master host is down, it fails.



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

[jira] [Created] (HAWQ-617) Add a flag to hawq config to allow skipping hosts on which ssh fails and continue with syncing configurations files

2016-04-01 Thread bhuvnesh chaudhary (JIRA)

bhuvnesh chaudhary created HAWQ-617:
---

 Summary: Add a flag to hawq config to allow skipping hosts on 
which ssh fails and continue with syncing configurations files
 Key: HAWQ-617
 URL: https://issues.apache.org/jira/browse/HAWQ-617
 Project: Apache HAWQ
  Issue Type: Bug
Reporter: bhuvnesh chaudhary
Assignee: Lei Chang


Add a flag to hawq config to allow skipping hosts on which ssh fails and 
continue with syncing configurations files.

Currently, if there is any one bad host, sync operations fails. Hawq activate 
standby uses hawq config to update hawq-site.xml configuration, however if the 
active master host is down, it fails.



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

37 matches

Mail list logo