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

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

GitHub user linwen opened a pull request:

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

    HAWQ-473. Insert a row into gp_configuration_history when segment sta…

    Implement adding a entry into gp_configuration_history when segment' status 
is changed, so that users can know the reason of status change by querying this 
catalog table.
    A cleanup function is needed when user decides to clear this table.
    Please review. Thanks

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

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

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

    https://github.com/apache/incubator-hawq/pull/396.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 #396
    
----
commit af0b1f6895824887a642b4891ce00473759d9631
Author: Wen Lin <w...@pivotal.io>
Date:   2016-02-29T09:35:23Z

    HAWQ-473. Insert a row into gp_configuration_history when segment status 
change

----


> Implement adding a entry into gp_configuration_history when segment' status 
> is changed
> --------------------------------------------------------------------------------------
>
>                 Key: HAWQ-473
>                 URL: https://issues.apache.org/jira/browse/HAWQ-473
>             Project: Apache HAWQ
>          Issue Type: Improvement
>          Components: Fault Tolerance, Resource Manager
>            Reporter: Lin Wen
>            Assignee: Lin Wen
>
> Implement adding a entry into gp_configuration_history when segment' status 
> is changed, so that users can know the reason of status change by querying 
> this catalog table.
> A cleanup function is needed when user decides to clear this table.



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

Reply via email to