[ 
https://issues.apache.org/jira/browse/YARN-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740238#comment-14740238
 ] 

Hadoop QA commented on YARN-4102:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | pre-patch |  16m  7s | Findbugs (version ) appears to 
be broken on YARN-2928. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any 
@author tags. |
| {color:red}-1{color} | tests included |   0m  0s | The patch doesn't appear 
to include any new or modified tests.  Please justify why no new tests are 
needed for this patch. Also please list what manual steps were performed to 
verify this patch. |
| {color:green}+1{color} | javac |   8m 10s | There were no new javac warning 
messages. |
| {color:green}+1{color} | javadoc |  10m 20s | There were no new javadoc 
warning messages. |
| {color:green}+1{color} | release audit |   0m 23s | The applied patch does 
not increase the total number of release audit warnings. |
| {color:green}+1{color} | checkstyle |   0m 17s | There were no new checkstyle 
issues. |
| {color:green}+1{color} | whitespace |   0m  0s | The patch has no lines that 
end in whitespace. |
| {color:green}+1{color} | install |   1m 34s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 40s | The patch built with 
eclipse:eclipse. |
| {color:green}+1{color} | findbugs |   0m 51s | The patch does not introduce 
any new Findbugs (version 3.0.0) warnings. |
| {color:green}+1{color} | yarn tests |   1m 35s | Tests passed in 
hadoop-yarn-server-timelineservice. |
| | |  40m  0s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12755269/YARN-4102-YARN-2928.004.patch
 |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | YARN-2928 / e6afe26 |
| hadoop-yarn-server-timelineservice test log | 
https://builds.apache.org/job/PreCommit-YARN-Build/9085/artifact/patchprocess/testrun_hadoop-yarn-server-timelineservice.txt
 |
| Test Results | 
https://builds.apache.org/job/PreCommit-YARN-Build/9085/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf907.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP 
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output | 
https://builds.apache.org/job/PreCommit-YARN-Build/9085/console |


This message was automatically generated.

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

Reply via email to