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

ASF GitHub Bot commented on TAJO-1673:
--------------------------------------

GitHub user blrunner opened a pull request:

    https://github.com/apache/tajo/pull/626

    TAJO-1673: Implement recover partitions

    This is still ongoing work. I'll do more tests and update DDLExecutor after 
committing TAJO-1345.

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

    $ git pull https://github.com/blrunner/tajo TAJO-1673

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

    https://github.com/apache/tajo/pull/626.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 #626
    
----
commit c66ab61ae0cf66f42fc44fbdd4394f87ec5b5700
Author: JaeHwa Jung <[email protected]>
Date:   2015-07-09T02:55:30Z

    Add msck repair table statment.

commit e3bd88f661722e38667f83b8d6cdafda03934a3b
Author: JaeHwa Jung <[email protected]>
Date:   2015-07-09T15:39:55Z

    Implement msck repair table on DDLExecutor.

----


> Implement recover partitions
> ----------------------------
>
>                 Key: TAJO-1673
>                 URL: https://issues.apache.org/jira/browse/TAJO-1673
>             Project: Tajo
>          Issue Type: Sub-task
>          Components: Catalog
>            Reporter: Jaehwa Jung
>            Assignee: Jaehwa Jung
>
> Tajo stores a list of partitions for each table in its CatalogStore. If, 
> however, new partitions are directly added to HDFS, the CatalogStore will not 
> be aware of these partitions unless the user runs ALTER TABLE table_name ADD 
> PARTITION commands on each of the newly added partitions.
> However, users can run a CatalogStore check command with the repair table 
> option:
> {code:xml}
> MSCK REPAIR TABLE <table_name>
> {code}
> For the reference, I've referenced hive msck command.



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

Reply via email to