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

Li Lu updated YARN-4102:
------------------------
    Attachment: YARN-4102-YARN-2928.002.patch

Thanks [~jrottinghuis] for the review! In the second version I changed the 
"force" mode into a mode called "skip on existing tables". I've also updated 
descriptions about this mode. 

> Add an "incremental" 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)

Reply via email to