[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15248958#comment-15248958 ] Andrew Purtell commented on HBASE-15665: bq. So can we remove the jdk8 javadoc check for 0.98 branch? [~apurtell] sure, +1. the 98 javadocs are not jdk8 clean. > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0 >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0 > > Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch, > HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15248278#comment-15248278 ] Hudson commented on HBASE-15665: ABORTED: Integrated in HBase-0.98-matrix #332 (See [https://builds.apache.org/job/HBase-0.98-matrix/332/]) HBASE-15665 Support using different StoreFileComparators for different (zhangduo: rev e956eb63deab0a69343e172dfb2e7428c914e754) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/DateTieredCompactionPolicy.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StripeStoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreEngine.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HStore.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DateTieredStoreEngine.java > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0 >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0 > > Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch, > HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15248225#comment-15248225 ] Hudson commented on HBASE-15665: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1204 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1204/]) HBASE-15665 Support using different StoreFileComparators for different (zhangduo: rev e956eb63deab0a69343e172dfb2e7428c914e754) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DateTieredStoreEngine.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/DateTieredCompactionPolicy.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HStore.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StripeStoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreEngine.java > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0 >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0 > > Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch, > HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15248017#comment-15248017 ] Hudson commented on HBASE-15665: FAILURE: Integrated in HBase-Trunk_matrix #856 (See [https://builds.apache.org/job/HBase-Trunk_matrix/856/]) HBASE-15665 Support using different StoreFileComparators for different (zhangduo: rev bd3b9753a9a792b402064ec4fabf2dc3c2eb41f1) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HStore.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreEngine.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/DateTieredCompactionPolicy.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StripeStoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DateTieredStoreEngine.java > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0 >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0 > > Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch, > HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[
https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247936#comment-15247936
]
Sean Busbey commented on HBASE-15665:
-
{quote}
So can we remove the jdk8 javadoc check for 0.98 branch? Andrew Purtell
Does yetus support running different checks for different branches? Sean Busbey
{quote}
Please see YETUS-369
> Support using different StoreFileComparators for different CompactionPolicies
> -
>
> Key: HBASE-15665
> URL: https://issues.apache.org/jira/browse/HBASE-15665
> Project: HBase
> Issue Type: Sub-task
> Components: Compaction
>Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0
>Reporter: Duo Zhang
>Assignee: Duo Zhang
> Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0
>
> Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch,
> HBASE-15665.patch
>
>
> Now for DateTieredCompactionPolicy, if we output multiple files when
> compaction, we will use the same max sequence id for all the output files(see
> HBASE-15389 for more details). So we need to sort the store files by
> timestamp if they have the same max sequence id which is different from the
> original store file comparator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247938#comment-15247938 ] Hudson commented on HBASE-15665: SUCCESS: Integrated in HBase-1.3-IT #621 (See [https://builds.apache.org/job/HBase-1.3-IT/621/]) HBASE-15665 Support using different StoreFileComparators for different (zhangduo: rev 8568b0cb81b767d1ac5508388a4ef1bd3994c3d3) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/DateTieredCompactionPolicy.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreEngine.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HStore.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StripeStoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DateTieredStoreEngine.java > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0 >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0 > > Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch, > HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247897#comment-15247897 ] Hudson commented on HBASE-15665: SUCCESS: Integrated in HBase-1.3 #657 (See [https://builds.apache.org/job/HBase-1.3/657/]) HBASE-15665 Support using different StoreFileComparators for different (zhangduo: rev 8568b0cb81b767d1ac5508388a4ef1bd3994c3d3) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DateTieredStoreEngine.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/DateTieredCompactionPolicy.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreEngine.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HStore.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StripeStoreFileManager.java > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0 >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0 > > Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch, > HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247830#comment-15247830 ] Duo Zhang commented on HBASE-15665: --- So can we remove the jdk8 javadoc check for 0.98 branch? [~apurtell] Does yetus support running different checks for different branches? [~busbey] And for the findbugs, let's file a issue to fix them, it is annoying... > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0 >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0 > > Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch, > HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247787#comment-15247787 ] Hudson commented on HBASE-15665: SUCCESS: Integrated in HBase-1.4 #99 (See [https://builds.apache.org/job/HBase-1.4/99/]) HBASE-15665 Support using different StoreFileComparators for different (zhangduo: rev 22b10610447c28466d0622ae71712f3097fecb0b) * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HStore.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreEngine.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/compactions/DateTieredCompactionPolicy.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StripeStoreFileManager.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DateTieredStoreEngine.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/DefaultStoreFileManager.java > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0 >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0 > > Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch, > HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[
https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247693#comment-15247693
]
Sean Busbey commented on HBASE-15665:
-
{quote}
For 0.98, the fingbugs and javadoc issues are not related, I have checked
already.
Sean Busbey Any ideas that why pre commit always report findbugs and javadoc
issue for 0.98?
{quote}
Those are the reports for the state of the branch prior to the patch being
applied. Those issues exist in the 0.98 branch, so they continue to show up.
This is the part that talks about after the patch:
{quote}
+1 findbugs4m 21s the patch passed
-1 javadoc 1m 33s hbase-server in the patch failed with JDK v1.8.0.
+1 javadoc 0m 40s the patch passed with JDK v1.7.0_79
{quote}
The failure of javadoc under jdk1.8 is real, but since it failed prior to the
patch it's hard to know if the patch makes things better or worse. AFAIK we
have never done a jdk8 compatibility pass on that branch.
> Support using different StoreFileComparators for different CompactionPolicies
> -
>
> Key: HBASE-15665
> URL: https://issues.apache.org/jira/browse/HBASE-15665
> Project: HBase
> Issue Type: Sub-task
> Components: Compaction
>Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0
>Reporter: Duo Zhang
>Assignee: Duo Zhang
> Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0
>
> Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch,
> HBASE-15665.patch
>
>
> Now for DateTieredCompactionPolicy, if we output multiple files when
> compaction, we will use the same max sequence id for all the output files(see
> HBASE-15389 for more details). So we need to sort the store files by
> timestamp if they have the same max sequence id which is different from the
> original store file comparator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247589#comment-15247589 ] Duo Zhang commented on HBASE-15665: --- The failed tests are unrelated. Will commit shortly. > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0 >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0 > > Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch, > HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[
https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247578#comment-15247578
]
Hadoop QA commented on HBASE-15665:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} 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} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 7m
13s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 34s
{color} | {color:green} branch-1 passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 30s
{color} | {color:green} branch-1 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
24s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
18s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
49s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 31s
{color} | {color:green} branch-1 passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 33s
{color} | {color:green} branch-1 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
41s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 34s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 34s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 31s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 31s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
19s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
13m 22s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
23s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 33s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 40s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 113m 27s
{color} | {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 145m 29s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestSplitTransactionOnCluster |
| Timed out junit tests |
org.apache.hadoop.hbase.replication.regionserver.TestRegionReplicaReplicationEndpoint
|
| | org.apache.hadoop.hbase.replication.TestReplicationSmallTests |
| | org.apache.hadoop.hbase.replication.TestReplicationStateZKImpl |
| |
org.apache.hadoop.hbase.replication.regionserver.TestReplicationWALReaderManager
|
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12799466/HBASE-15665-branch-1.patch
|
| JIRA Issue | HBASE-15665 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[
https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247373#comment-15247373
]
Hadoop QA commented on HBASE-15665:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} 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} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 5m
57s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 33s
{color} | {color:green} branch-1 passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 30s
{color} | {color:green} branch-1 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
24s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
20s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
49s {color} | {color:green} branch-1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 36s
{color} | {color:green} branch-1 passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 33s
{color} | {color:green} branch-1 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
41s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 43s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 43s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 31s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 31s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
18s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
11m 37s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 5s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 33s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 15m 38s {color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
16s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 44m 22s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.regionserver.TestDateTieredCompactionPolicy
|
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12799453/HBASE-15665-branch-1.patch
|
| JIRA Issue | HBASE-15665 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| 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 |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
|
| git revision | branch-1 / 2b5da6f |
| Default Java | 1.7.0_79
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247346#comment-15247346 ] Duo Zhang commented on HBASE-15665: --- For 0.98, the fingbugs and javadoc issues are not related, I have checked already. [~busbey] Any ideas that why pre commit always report findbugs and javadoc issue for 0.98? Thanks. > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Affects Versions: 2.0.0, 1.3.0, 0.98.19, 1.4.0 >Reporter: Duo Zhang >Assignee: Duo Zhang > Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0 > > Attachments: HBASE-15665-0.98.patch, HBASE-15665-branch-1.patch, > HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[
https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247233#comment-15247233
]
Hadoop QA commented on HBASE-15665:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} 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} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
25s {color} | {color:green} 0.98 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 27s
{color} | {color:green} 0.98 passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 3s
{color} | {color:green} 0.98 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
27s {color} | {color:green} 0.98 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
26s {color} | {color:green} 0.98 passed {color} |
| {color:red}-1{color} | {color:red} findbugs {color} | {color:red} 3m 36s
{color} | {color:red} hbase-server in 0.98 has 84 extant Findbugs warnings.
{color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 1m 28s
{color} | {color:red} hbase-server in 0.98 failed with JDK v1.8.0. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 3s
{color} | {color:green} 0.98 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 46s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 46s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 9s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 9s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
32s {color} | {color:green} hbase-server: patch generated 0 new + 20 unchanged
- 3 fixed = 20 total (was 23) {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
32s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
21m 29s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
21s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 1m 33s
{color} | {color:red} hbase-server in the patch failed with JDK v1.8.0. {color}
|
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m 22s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 55m 42s {color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
56s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 104m 31s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.replication.regionserver.TestReplicationThrottler |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12799433/HBASE-15665-0.98.patch
|
| JIRA Issue | HBASE-15665 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| uname | Linux asf900.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 |
| Build tool | maven |
| Personality |
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15247019#comment-15247019 ] Ted Yu commented on HBASE-15665: Right. I don't have other comment. > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Reporter: Duo Zhang >Assignee: Duo Zhang > Attachments: HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[
https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246968#comment-15246968
]
Duo Zhang commented on HBASE-15665:
---
{quote}
This method can be package private, right ?
{quote}
This is an interface so only public method is allowed...
> Support using different StoreFileComparators for different CompactionPolicies
> -
>
> Key: HBASE-15665
> URL: https://issues.apache.org/jira/browse/HBASE-15665
> Project: HBase
> Issue Type: Sub-task
> Components: Compaction
>Reporter: Duo Zhang
>Assignee: Duo Zhang
> Attachments: HBASE-15665.patch
>
>
> Now for DateTieredCompactionPolicy, if we output multiple files when
> compaction, we will use the same max sequence id for all the output files(see
> HBASE-15389 for more details). So we need to sort the store files by
> timestamp if they have the same max sequence id which is different from the
> original store file comparator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[
https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246425#comment-15246425
]
Ted Yu commented on HBASE-15665:
{code}
172 Comparator getStoreFileComparator();
{code}
This method can be package private, right ?
> Support using different StoreFileComparators for different CompactionPolicies
> -
>
> Key: HBASE-15665
> URL: https://issues.apache.org/jira/browse/HBASE-15665
> Project: HBase
> Issue Type: Sub-task
> Components: Compaction
>Reporter: Duo Zhang
>Assignee: Duo Zhang
> Attachments: HBASE-15665.patch
>
>
> Now for DateTieredCompactionPolicy, if we output multiple files when
> compaction, we will use the same max sequence id for all the output files(see
> HBASE-15389 for more details). So we need to sort the store files by
> timestamp if they have the same max sequence id which is different from the
> original store file comparator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15246261#comment-15246261 ] Dave Latham commented on HBASE-15665: - Looks good to me. > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Reporter: Duo Zhang >Assignee: Duo Zhang > Attachments: HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15245470#comment-15245470 ] Duo Zhang commented on HBASE-15665: --- [~clarax98007] This can remove the extra sort in DateTieredCompactionPolicy. And this comparator will also be used to sort filesCompacting, which can be more reliable if we want to check overlapping when archiving. Thanks. > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Reporter: Duo Zhang >Assignee: Duo Zhang > Attachments: HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[ https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15245087#comment-15245087 ] Duo Zhang commented on HBASE-15665: --- Trivial change so no new tests. > Support using different StoreFileComparators for different CompactionPolicies > - > > Key: HBASE-15665 > URL: https://issues.apache.org/jira/browse/HBASE-15665 > Project: HBase > Issue Type: Sub-task > Components: Compaction >Reporter: Duo Zhang >Assignee: Duo Zhang > Attachments: HBASE-15665.patch > > > Now for DateTieredCompactionPolicy, if we output multiple files when > compaction, we will use the same max sequence id for all the output files(see > HBASE-15389 for more details). So we need to sort the store files by > timestamp if they have the same max sequence id which is different from the > original store file comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-15665) Support using different StoreFileComparators for different CompactionPolicies
[
https://issues.apache.org/jira/browse/HBASE-15665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15244725#comment-15244725
]
Hadoop QA commented on HBASE-15665:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s
{color} | {color:red} 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} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
5s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 45s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 31s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 4m
17s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
16s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
50s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 26s
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 33s
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
42s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 37s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 31s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 31s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 4m
34s {color} | {color:green} hbase-server: patch generated 0 new + 68 unchanged
- 1 fixed = 68 total (was 69) {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
15s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
25m 33s {color} | {color:green} Patch does not cause any errors with Hadoop
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 6s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 26s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 34s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 92m 51s {color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
16s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 140m 38s {color}
| {color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests |
hadoop.hbase.security.visibility.TestVisibilityLabelsWithDeletes |
| Timed out junit tests |
org.apache.hadoop.hbase.security.access.TestNamespaceCommands |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12799135/HBASE-15665.patch |
| JIRA Issue | HBASE-15665 |
| Optional Tests | asflicense javac javadoc unit findbugs hadoopcheck
hbaseanti checkstyle compile |
| 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 |
| Build tool | maven |
| Personality |
