You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by blrunner <gi...@git.apache.org> on 2016/04/12 09:11:00 UTC

[GitHub] tajo pull request: TAJO-2087: Support DirectOutputCommitter for AW...

Github user blrunner commented on the pull request:

    https://github.com/apache/tajo/pull/979#issuecomment-208744154
  
    I designed the table of direct output commit history as following:
    
    Column Name | Column Type | Null | Desc
    -------------------|----------------------|--------------------------|-------------------
    QUERY_ID | VARCHAR(128) | NOT NULL | the id of ``Query``, PRIMARY KEY
    PATH | VARCHAR(4096) | NOT NULL  | the output path of table
    START_TIME | BIGINT | NOT NULL | query start time
    END_TIME |  BIGINT | | query finish time
    QUERY_STATE | VARCHAR(50) | NOT NULL | the state of ``Query``, ``TajoProtos.QueryState`` will be used
    
    Implemented necessary codes to ``Query`` and ``TajoMaster`` as following:
    * When query starting, add the history to catalog.
    * If query fails, ``QueryMaster`` will delete committed files and update the status of output commit history to catalog
    * When ``TajoMaster`` starting, it will check the status of output commit histories to catalog. If it find running query, it will delete committed files and update the status of output commit history.
    
    Not yet implemented unit test cases for failed queries.



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