[
https://issues.apache.org/jira/browse/YARN-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369794#comment-15369794
]
Hudson commented on YARN-4102:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #10074 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10074/])
YARN-4102. Add a "skip existing table" mode for timeline schema creator (sjlee:
rev ee081018e4806cc89769d95c85ad7a49b780f073)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-timelineservice/src/main/java/org/apache/hadoop/yarn/server/timelineservice/storage/TimelineSchemaCreator.java
> 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
> Fix For: YARN-2928
>
> Attachments: YARN-4102-YARN-2928.001.patch,
> YARN-4102-YARN-2928.002.patch, YARN-4102-YARN-2928.003.patch,
> YARN-4102-YARN-2928.004.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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
