hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Li Lu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-4102) Add an "incremental" mode for timeline schema creator
Date Tue, 01 Sep 2015 22:24:47 GMT

     [ 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.001.patch

Instead of an "incremental" mode I added a "force" mode that will continue to create all hbase
tables even if exceptions occur. This option is (of course) turned off by default and is supposed
to be used mainly by devs. 

One thing makes me really painful is the long try-catch statements for all hbase tables. I'm
trying my best to keep code duplication in a low level, but due to the generic types of the
tables, I have to perform try-catch for each one of the table creations. 

I've also cleaned up all short options. After centralize them I hope it's easier to avoid
option short name collisions. 

> 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
> 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

View raw message