You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Li Lu (JIRA)" <ji...@apache.org> on 2015/09/02 22:41:46 UTC

[jira] [Updated] (YARN-4102) Add a "skip existing table" mode for timeline schema creator

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

Li Lu updated YARN-4102:
------------------------
    Summary: Add a "skip existing table" mode for timeline schema creator  (was: Add an "incremental" mode for timeline schema creator)

> Add a "skip existing table" mode for timeline schema creator
> ------------------------------------------------------------
>
>                 Key: YARN-4102
>                 URL: https://issues.apache.org/jira/browse/YARN-4102
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Li Lu
>            Assignee: Li Lu
>         Attachments: YARN-4102-YARN-2928.001.patch, YARN-4102-YARN-2928.002.patch
>
>
> When debugging timeline POCs, we may need to create hbase tables that are added in some ongoing patches. Right now, our schema creator will exit when it hits one existing table. While this is a correct behavior with end users, this introduces much trouble in debugging POCs: every time we have to disable all existing tables, drop them, run the schema creator to generate all tables, and regenerate all test data. 
> Maybe we'd like to add an "incremental" mode so that the creator will only create non-existing tables? This is pretty handy in deploying our POCs. Of course, consistency has to be kept in mind across tables. 



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