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

Hadoop QA commented on YARN-3411:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  15m 36s | Pre-patch YARN-2928 compilation 
is healthy. |
| {color:green}+1{color} | @author |   0m  0s | The patch does not contain any 
@author tags. |
| {color:green}+1{color} | tests included |   0m  0s | The patch appears to 
include 1 new or modified test files. |
| {color:green}+1{color} | javac |   7m 44s | There were no new javac warning 
messages. |
| {color:red}-1{color} | javadoc |   9m 40s | The applied patch generated  11  
additional 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 14s | 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 38s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 40s | The patch built with 
eclipse:eclipse. |
| {color:red}-1{color} | findbugs |   0m 42s | The patch appears to introduce 8 
new Findbugs (version 2.0.3) warnings. |
| {color:red}-1{color} | yarn tests |   7m 50s | Tests failed in 
hadoop-yarn-server-timelineservice. |
| | |  44m 34s | |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hadoop-yarn-server-timelineservice |
|  |  
org.apache.hadoop.yarn.server.timelineservice.storage.EntityColumnDetails.getInBytes()
 may expose internal representation by returning EntityColumnDetails.inBytes  
At EntityColumnDetails.java:by returning EntityColumnDetails.inBytes  At 
EntityColumnDetails.java:[line 48] |
|  |  
org.apache.hadoop.yarn.server.timelineservice.storage.EntityTableDetails.COLUMN_FAMILY_CONFIG_BYTES
 should be package protected  At EntityTableDetails.java: At 
EntityTableDetails.java:[line 48] |
|  |  
org.apache.hadoop.yarn.server.timelineservice.storage.EntityTableDetails.COLUMN_FAMILY_INFO_BYTES
 should be package protected  At EntityTableDetails.java: At 
EntityTableDetails.java:[line 34] |
|  |  
org.apache.hadoop.yarn.server.timelineservice.storage.EntityTableDetails.COLUMN_FAMILY_METRICS_BYTES
 should be package protected  At EntityTableDetails.java: At 
EntityTableDetails.java:[line 41] |
|  |  
org.apache.hadoop.yarn.server.timelineservice.storage.EntityTableDetails.COLUMN_PREFIX_EVENTS_BYTES
 should be package protected  At EntityTableDetails.java: At 
EntityTableDetails.java:[line 55] |
|  |  
org.apache.hadoop.yarn.server.timelineservice.storage.EntityTableDetails.COLUMN_PREFIX_IS_RELATED_TO_BYTES
 should be package protected  At EntityTableDetails.java: At 
EntityTableDetails.java:[line 69] |
|  |  
org.apache.hadoop.yarn.server.timelineservice.storage.EntityTableDetails.COLUMN_PREFIX_RELATES_TO_BYTES
 should be package protected  At EntityTableDetails.java: At 
EntityTableDetails.java:[line 62] |
|  |  
org.apache.hadoop.yarn.server.timelineservice.storage.EntityTableDetails.ROW_KEY_SEPARATOR_BYTES
 should be package protected  At EntityTableDetails.java: At 
EntityTableDetails.java:[line 79] |
| Failed unit tests | 
hadoop.yarn.server.timelineservice.storage.TestHBaseTimelineWriterImpl |
|   | hadoop.yarn.server.timelineservice.storage.TestPhoenixTimelineWriterImpl |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | 
http://issues.apache.org/jira/secure/attachment/12732791/YARN-3411-YARN-2928.001.patch
 |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | YARN-2928 / b059dd4 |
| javadoc | 
https://builds.apache.org/job/PreCommit-YARN-Build/7932/artifact/patchprocess/diffJavadocWarnings.txt
 |
| Findbugs warnings | 
https://builds.apache.org/job/PreCommit-YARN-Build/7932/artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-timelineservice.html
 |
| hadoop-yarn-server-timelineservice test log | 
https://builds.apache.org/job/PreCommit-YARN-Build/7932/artifact/patchprocess/testrun_hadoop-yarn-server-timelineservice.txt
 |
| Test Results | 
https://builds.apache.org/job/PreCommit-YARN-Build/7932/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf901.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/7932/console |


This message was automatically generated.

> [Storage implementation] explore the native HBase write schema for storage
> --------------------------------------------------------------------------
>
>                 Key: YARN-3411
>                 URL: https://issues.apache.org/jira/browse/YARN-3411
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Sangjin Lee
>            Assignee: Vrushali C
>            Priority: Critical
>         Attachments: ATSv2BackendHBaseSchemaproposal.pdf, 
> YARN-3411-YARN-2928.001.patch, YARN-3411.poc.2.txt, YARN-3411.poc.3.txt, 
> YARN-3411.poc.4.txt, YARN-3411.poc.5.txt, YARN-3411.poc.6.txt, 
> YARN-3411.poc.7.txt, YARN-3411.poc.txt
>
>
> There is work that's in progress to implement the storage based on a Phoenix 
> schema (YARN-3134).
> In parallel, we would like to explore an implementation based on a native 
> HBase schema for the write path. Such a schema does not exclude using 
> Phoenix, especially for reads and offline queries.
> Once we have basic implementations of both options, we could evaluate them in 
> terms of performance, scalability, usability, etc. and make a call.



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

Reply via email to