[jira] [Commented] (HBASE-18902) TestCoprocessorServiceBackwardCompatibility fails in master branch
[
https://issues.apache.org/jira/browse/HBASE-18902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187646#comment-16187646
]
Appy commented on HBASE-18902:
--
Saving ~20 sec on these tests by merging them together makes sense.
Thanks for the data [~tedyu]. +1 on v4
> TestCoprocessorServiceBackwardCompatibility fails in master branch
> --
>
> Key: HBASE-18902
> URL: https://issues.apache.org/jira/browse/HBASE-18902
> Project: HBase
> Issue Type: Test
>Reporter: Ted Yu
>Assignee: Ted Yu
> Attachments: 18902.v1.txt, 18902.v2.txt, 18902.v3.txt, 18902.v4.txt,
> HBASE-18902.master.001.patch, HBASE-18902.master.001.patch
>
>
> Starting mini cluster in subtests without shutting down resulted in:
> {code}
> java.lang.IllegalStateException: A mini-cluster is already running
> at
> org.apache.hadoop.hbase.coprocessor.TestCoprocessorServiceBackwardCompatibility.testCoprocessorServiceLoadedByRegion(TestCoprocessorServiceBackwardCompatibility.java:109)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18891) Upgrade netty-all jar
[
https://issues.apache.org/jira/browse/HBASE-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187640#comment-16187640
]
Hadoop QA commented on HBASE-18891:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
22s{color} | {color:blue} Docker mode activated. {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} 1m
54s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
23s{color} | {color:green} branch-1.3 passed with JDK v1.8.0_144 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
18s{color} | {color:green} branch-1.3 passed with JDK v1.7.0_151 {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
37s{color} | {color:green} branch-1.3 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 7m
32s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
40s{color} | {color:green} branch-1.3 passed with JDK v1.8.0_144 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
26s{color} | {color:green} branch-1.3 passed with JDK v1.7.0_151 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
49s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
22s{color} | {color:green} the patch passed with JDK v1.8.0_144 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
20s{color} | {color:green} the patch passed with JDK v1.7.0_151 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
20s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
36s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
1s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:red}-1{color} | {color:red} shadedjars {color} | {color:red} 0m
43s{color} | {color:red} patch has 11 errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
16m 37s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
46s{color} | {color:green} the patch passed with JDK v1.8.0_144 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 2m
25s{color} | {color:green} the patch passed with JDK v1.7.0_151 {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red}344m 48s{color}
| {color:red} root in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 3m
8s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}386m 28s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.master.balancer.TestStochasticLoadBalancer |
| | hadoop.hbase.replication.regionserver.TestReplicator |
| | hadoop.hbase.client.TestAdmin2 |
| Timed out junit tests |
org.apache.hadoop.hbase.master.procedure.TestModifyTableProcedure |
| | org.apache.hadoop.hbase.master.procedure.TestServerCrashProcedure |
| | org.apache.hadoop.hbase.regionserver.TestCorruptedRegionStoreFile |
| | org.apache.hadoop.hbase.regionserver.compactions.TestFIFOCompactionPolicy
|
| | org.apache.hadoop.hbase.master.TestMasterFailover |
| | org.apache.hadoop.hbase.snapshot.TestSnapshotClientRetries |
| | org.apache.hadoop.hbase.master.TestAssignmentManagerMetrics |
| |
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187636#comment-16187636 ] Hudson commented on HBASE-17441: SUCCESS: Integrated in Jenkins build HBase-1.3-JDK8 #301 (See [https://builds.apache.org/job/HBase-1.3-JDK8/301/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (busbey: rev d01b15f83fd465b1b75380122efe1e87b7909bed) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187623#comment-16187623 ] Hudson commented on HBASE-17441: SUCCESS: Integrated in Jenkins build HBase-1.2-JDK8 #224 (See [https://builds.apache.org/job/HBase-1.2-JDK8/224/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (busbey: rev 54ecaa94e4beb0b6d3a08de4b138fe193a804017) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187621#comment-16187621 ] Hudson commented on HBASE-17441: SUCCESS: Integrated in Jenkins build HBase-1.4 #938 (See [https://builds.apache.org/job/HBase-1.4/938/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (busbey: rev c3697bd2739db6de3ba337efadb7e543113a6477) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187619#comment-16187619 ] Hudson commented on HBASE-17441: FAILURE: Integrated in Jenkins build HBase-1.5 #82 (See [https://builds.apache.org/job/HBase-1.5/82/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (busbey: rev 61173522ddd38f6a0aa8363e4421e910b839) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187617#comment-16187617 ] Hudson commented on HBASE-17441: SUCCESS: Integrated in Jenkins build HBase-1.1-JDK8 #1999 (See [https://builds.apache.org/job/HBase-1.1-JDK8/1999/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (busbey: rev ea67acab70f87eb3a15119c2f4a393e2a12d8527) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187609#comment-16187609 ] Hudson commented on HBASE-17441: SUCCESS: Integrated in Jenkins build HBase-1.1-JDK7 #1915 (See [https://builds.apache.org/job/HBase-1.1-JDK7/1915/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (busbey: rev ea67acab70f87eb3a15119c2f4a393e2a12d8527) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187601#comment-16187601 ] Hudson commented on HBASE-17441: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3810 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3810/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (elserj: rev 869b90c612ebf2f931dcd43be59b817e4b55ab32) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18409) Migrate Client Metrics from codahale to hbase-metrics
[
https://issues.apache.org/jira/browse/HBASE-18409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187597#comment-16187597
]
Hadoop QA commented on HBASE-18409:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
17s{color} | {color:blue} Docker mode activated. {color} |
| {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 7 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
33s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
55s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
36s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
44s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
23s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
47s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
6s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
17s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
23s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
37s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
44s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch 1 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m
3s{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
0s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
37m 3s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
23s{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
28s{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
30s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 70m 53s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 1m
46s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}139m 56s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Timed out junit tests |
org.apache.hadoop.hbase.client.TestAsyncReplicationAdminApi |
| | org.apache.hadoop.hbase.snapshot.TestSnapshotClientRetries |
| | org.apache.hadoop.hbase.coprocessor.TestRegionObserverScannerOpenHook |
| |
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187592#comment-16187592 ] Hudson commented on HBASE-17441: FAILURE: Integrated in Jenkins build HBase-2.0 #609 (See [https://builds.apache.org/job/HBase-2.0/609/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (elserj: rev 8c6ed571bdbbd3eb5fe38aa0833124ca75c19cfa) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187589#comment-16187589 ] Hudson commented on HBASE-17441: SUCCESS: Integrated in Jenkins build HBase-1.2-IT #961 (See [https://builds.apache.org/job/HBase-1.2-IT/961/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (busbey: rev 54ecaa94e4beb0b6d3a08de4b138fe193a804017) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187585#comment-16187585 ] Hudson commented on HBASE-17441: SUCCESS: Integrated in Jenkins build HBase-1.3-IT #218 (See [https://builds.apache.org/job/HBase-1.3-IT/218/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (busbey: rev d01b15f83fd465b1b75380122efe1e87b7909bed) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187579#comment-16187579 ] Hudson commented on HBASE-17441: FAILURE: Integrated in Jenkins build HBase-1.3-JDK7 #290 (See [https://builds.apache.org/job/HBase-1.3-JDK7/290/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (busbey: rev d01b15f83fd465b1b75380122efe1e87b7909bed) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187581#comment-16187581 ] Hudson commented on HBASE-17441: FAILURE: Integrated in Jenkins build HBase-1.2-JDK7 #228 (See [https://builds.apache.org/job/HBase-1.2-JDK7/228/]) HBASE-17441 Fix invalid quoting around hadoop-3 build in yetus (busbey: rev 54ecaa94e4beb0b6d3a08de4b138fe193a804017) * (edit) dev-support/hbase-personality.sh > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187577#comment-16187577 ] Sean Busbey commented on HBASE-17441: - FYI, I pushed this to the branch-1* branches so that the yetus personality would be consistent across all branches. > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18409) Migrate Client Metrics from codahale to hbase-metrics
[ https://issues.apache.org/jira/browse/HBASE-18409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ronald Macmaster updated HBASE-18409: - Attachment: 0004-HBASE-18409-MetricsConnection-client-metrics-migration.patch Made sure this patch applies to upstream/master > Migrate Client Metrics from codahale to hbase-metrics > - > > Key: HBASE-18409 > URL: https://issues.apache.org/jira/browse/HBASE-18409 > Project: HBase > Issue Type: Improvement > Components: Client, java, metrics >Affects Versions: 3.0.0 >Reporter: Ronald Macmaster > Labels: newbie > Fix For: 3.0.0 > > Attachments: > 0001-HBASE-18409-MetricsConnection-client-metrics-migration.patch, > 0002-HBASE-18409-MetricsConnection-client-metrics-migrati.patch, > 0003-HBASE-18409-MetricsConnection-client-metrics-migration.patch, > 0004-HBASE-18409-MetricsConnection-client-metrics-migration.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > Currently, the metrics for hbase-client are tailored for reporting via a > client-side JMX server. > The MetricsConnection handles the metrics management and reporting via the > metrics platform from codahale. > This approach worked well for hbase-1.3.1 when the metrics platform was still > relatively young, but it could be improved by using the new > hbase-metrics-api. > Now that we have an actual hbase-metrics-api that master, regionserver, > zookeeper, and other daemons use, it would be good to also allow the client > to leverage the metrics-api. > Then, the client could also report its metrics via Hadoop's metrics2 if > desired or through another platform that utilizes the hbase-metrics-api. > If left alone, client metrics will continue to be only barely visible through > a client-side JMX server. > The migration to the new metrics-api could be done by simply changing the > Metrics data types from codahale types to hbase-metrics types without > changing the metrics signatures of MetricsConnection unless completely > necessary. > The codahale MetricsRegistry would also have to be exchanged for a > hbase-metrics MetricsRegistry. > I found this to be a necessary change after attempting to implement my own > Reporter to use within the MetricsConnection class. > I was attempting to create a HadoopMetrics2Reporter that extends the codahale > ScheduledReporter and reports the MetricsConnection metrics to Hadoop's > metrics2 system. > The already existing infrastructure in the hbase-metrics and > hbase-metrics-api projects could be easily leveraged for a cleaner solution. > If completed successfully, users could instead access their client-side > metrics through the hbase-metrics-api. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18753) Introduce the unsynchronized TimeRangeTracker
[ https://issues.apache.org/jira/browse/HBASE-18753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187530#comment-16187530 ] Hudson commented on HBASE-18753: SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #3809 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3809/]) HBASE-18753 Introduce the unsynchronized TimeRangeTracker (chia7712: rev 9f1bfbeaab7b8eb4bb9cfbc6ccab959b025fc7cd) * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/AbstractTestDateTieredCompactionPolicy.java * (add) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSimpleTimeRangeTracker.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileWriter.java * (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/util/ClassSize.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/TimeRangeTracker.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/io/TestHeapSize.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompositeImmutableSegment.java * (edit) hbase-mapreduce/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHFileOutputFormat2.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestDefaultCompactSelection.java * (delete) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestTimeRangeTracker.java * (add) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSyncTimeRangeTracker.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Segment.java > Introduce the unsynchronized TimeRangeTracker > - > > Key: HBASE-18753 > URL: https://issues.apache.org/jira/browse/HBASE-18753 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18753.v0.patch, HBASE-18753.v1.patch, > HBASE-18753.v2.patch, HBASE-18753.v3.patch, HBASE-18753.v4.patch > > > If HBASE-18752 is pushed, it will be better to introduce the unsync > TimeRangeTracker for reducing the cost of recalculation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18409) Migrate Client Metrics from codahale to hbase-metrics
[ https://issues.apache.org/jira/browse/HBASE-18409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187527#comment-16187527 ] Josh Elser commented on HBASE-18409: Hey [~qwerty2.0], thanks for making the time to turn around the fixes! I'm trying to piece together what your third patch is. It looks like this is a delta on top of your 2nd patch to me, but I'm not certain. Assuming that is the case, could you rebase and squash your changes on top of the current master branch and put up a new patch? If you're busy, I'll try to do it Monday (assuming I can figure out the inevitable conflicts ;)). > Migrate Client Metrics from codahale to hbase-metrics > - > > Key: HBASE-18409 > URL: https://issues.apache.org/jira/browse/HBASE-18409 > Project: HBase > Issue Type: Improvement > Components: Client, java, metrics >Affects Versions: 3.0.0 >Reporter: Ronald Macmaster > Labels: newbie > Fix For: 3.0.0 > > Attachments: > 0001-HBASE-18409-MetricsConnection-client-metrics-migration.patch, > 0002-HBASE-18409-MetricsConnection-client-metrics-migrati.patch, > 0003-HBASE-18409-MetricsConnection-client-metrics-migration.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > Currently, the metrics for hbase-client are tailored for reporting via a > client-side JMX server. > The MetricsConnection handles the metrics management and reporting via the > metrics platform from codahale. > This approach worked well for hbase-1.3.1 when the metrics platform was still > relatively young, but it could be improved by using the new > hbase-metrics-api. > Now that we have an actual hbase-metrics-api that master, regionserver, > zookeeper, and other daemons use, it would be good to also allow the client > to leverage the metrics-api. > Then, the client could also report its metrics via Hadoop's metrics2 if > desired or through another platform that utilizes the hbase-metrics-api. > If left alone, client metrics will continue to be only barely visible through > a client-side JMX server. > The migration to the new metrics-api could be done by simply changing the > Metrics data types from codahale types to hbase-metrics types without > changing the metrics signatures of MetricsConnection unless completely > necessary. > The codahale MetricsRegistry would also have to be exchanged for a > hbase-metrics MetricsRegistry. > I found this to be a necessary change after attempting to implement my own > Reporter to use within the MetricsConnection class. > I was attempting to create a HadoopMetrics2Reporter that extends the codahale > ScheduledReporter and reports the MetricsConnection metrics to Hadoop's > metrics2 system. > The already existing infrastructure in the hbase-metrics and > hbase-metrics-api projects could be easily leveraged for a cleaner solution. > If completed successfully, users could instead access their client-side > metrics through the hbase-metrics-api. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18891) Upgrade netty-all jar
[ https://issues.apache.org/jira/browse/HBASE-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-18891: --- Attachment: HBASE-18891.002.branch-1.3.patch Re-attaching .002. Rerunning the previously failed tests locally with some success. Let's hope that weekend QA bot is a little more reliable that weekday QA bot. > Upgrade netty-all jar > - > > Key: HBASE-18891 > URL: https://issues.apache.org/jira/browse/HBASE-18891 > Project: HBase > Issue Type: Bug >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: 1.3.2, 1.2.7, 1.1.13 > > Attachments: HBASE-18891.001.branch-1.3.patch, > HBASE-18891.002.branch-1.3.patch > > > Upgrade netty-all jar to 4.0.37.Final version to fix latest vulnerabilities > reported. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18891) Upgrade netty-all jar
[ https://issues.apache.org/jira/browse/HBASE-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-18891: --- Attachment: (was: HBASE-18891.002.branch-1.3.patch) > Upgrade netty-all jar > - > > Key: HBASE-18891 > URL: https://issues.apache.org/jira/browse/HBASE-18891 > Project: HBase > Issue Type: Bug >Reporter: Josh Elser >Assignee: Josh Elser >Priority: Critical > Fix For: 1.3.2, 1.2.7, 1.1.13 > > Attachments: HBASE-18891.001.branch-1.3.patch > > > Upgrade netty-all jar to 4.0.37.Final version to fix latest vulnerabilities > reported. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-17441: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Thanks for the help in getting to the bottom of this one, Sean & Appy! > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-17441: --- Fix Version/s: (was: 2.0.0) 2.0.0-alpha-4 > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0-alpha-4 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18753) Introduce the unsynchronized TimeRangeTracker
[ https://issues.apache.org/jira/browse/HBASE-18753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187510#comment-16187510 ] Hudson commented on HBASE-18753: FAILURE: Integrated in Jenkins build HBase-2.0 #608 (See [https://builds.apache.org/job/HBase-2.0/608/]) HBASE-18753 Introduce the unsynchronized TimeRangeTracker (chia7712: rev 2cc1ea3d2e814c60cdffaed2cc111e1578516143) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreFileWriter.java * (add) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSyncTimeRangeTracker.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/TimeRangeTracker.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompositeImmutableSegment.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/io/TestHeapSize.java * (delete) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestTimeRangeTracker.java * (edit) hbase-mapreduce/src/test/java/org/apache/hadoop/hbase/mapreduce/TestHFileOutputFormat2.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestDefaultCompactSelection.java * (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/util/ClassSize.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Segment.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/AbstractTestDateTieredCompactionPolicy.java * (add) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestSimpleTimeRangeTracker.java > Introduce the unsynchronized TimeRangeTracker > - > > Key: HBASE-18753 > URL: https://issues.apache.org/jira/browse/HBASE-18753 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18753.v0.patch, HBASE-18753.v1.patch, > HBASE-18753.v2.patch, HBASE-18753.v3.patch, HBASE-18753.v4.patch > > > If HBASE-18752 is pushed, it will be better to introduce the unsync > TimeRangeTracker for reducing the cost of recalculation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-17441) precommit test "hadoopcheck" not properly testing Hadoop 3 profile
[ https://issues.apache.org/jira/browse/HBASE-17441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187504#comment-16187504 ] Josh Elser commented on HBASE-17441: Thanks Appy. Will commit now that we got a -1 from PreCommit :P -- last time I'll ever get to say that. > precommit test "hadoopcheck" not properly testing Hadoop 3 profile > -- > > Key: HBASE-17441 > URL: https://issues.apache.org/jira/browse/HBASE-17441 > Project: HBase > Issue Type: Bug > Components: build >Affects Versions: 2.0.0 >Reporter: Sean Busbey >Assignee: Josh Elser >Priority: Blocker > Fix For: 2.0.0 > > Attachments: HBASE-17441.001.branch-2.patch, > HBASE-17441.002.branch-2.patch, HBASE-17441.0.patch > > > HBASE-14061 made a change that caused building against hadoop 3 to fail, but > the hadoopcheck precommit test gave the change a +1. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18897) Substitute MemStore for Memstore
[
https://issues.apache.org/jira/browse/HBASE-18897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187468#comment-16187468
]
Hadoop QA commented on HBASE-18897:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
| {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 28 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
16s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
35s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
18s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
55s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
15s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 6m
7s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 7m
14s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
38s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
17s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
31s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 2m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} cc {color} | {color:green} 2m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 2m
16s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
56s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 1m
15s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} whitespace {color} | {color:red} 0m
0s{color} | {color:red} The patch 1 line(s) with tabs. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
57s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
36m 15s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} hbaseprotoc {color} | {color:green}
1m 45s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 8m
12s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
28s{color} | {color:green} hbase-protocol-shaded in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
22s{color} | {color:green} hbase-hadoop-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
27s{color} | {color:green} hbase-hadoop2-compat in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m
18s{color} | {color:green} hbase-protocol in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
33s{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 90m
33s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 1m 17s{color}
| {color:red} hbase-rest in the patch failed. {color}
[jira] [Commented] (HBASE-13844) Move static helper methods from KeyValue into CellUtils
[ https://issues.apache.org/jira/browse/HBASE-13844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187439#comment-16187439 ] Hudson commented on HBASE-13844: FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3808 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3808/]) HBASE-13844 (Addendum) Replace KeyValue#isDelete by CellUtil#isDelete in (chia7712: rev dd3d7de018f15b24311c007e795798582c39) * (edit) hbase-shell/src/main/ruby/hbase/table.rb > Move static helper methods from KeyValue into CellUtils > --- > > Key: HBASE-13844 > URL: https://issues.apache.org/jira/browse/HBASE-13844 > Project: HBase > Issue Type: Improvement >Reporter: Lars George >Assignee: Andy Yang >Priority: Minor > Labels: beginner > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-13844.1.patch, HBASE-13844.2.patch, > HBASE-13844.3.patch, HBASE-13844.branch-2.v0.patch, > HBASE-13844.branch-2.v1.patch, HBASE-13844.branch-2.v2.patch, > HBASE-13844.branch-2.v3.patch, HBASE-13844.branch-2.v4.patch, > HBASE-13844.branch-2.v4.patch, HBASE-13844.branch-2.v5.patch > > > Add KeyValue.parseColumn() to CellUtils (also any other public static helper) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-13844) Move static helper methods from KeyValue into CellUtils
[ https://issues.apache.org/jira/browse/HBASE-13844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187417#comment-16187417 ] Hudson commented on HBASE-13844: FAILURE: Integrated in Jenkins build HBase-2.0 #607 (See [https://builds.apache.org/job/HBase-2.0/607/]) HBASE-13844 (Addendum) Replace KeyValue#isDelete by CellUtil#isDelete in (chia7712: rev f04bd9ca1816e565ac35c6513669e7e5544b9069) * (edit) hbase-shell/src/main/ruby/hbase/table.rb > Move static helper methods from KeyValue into CellUtils > --- > > Key: HBASE-13844 > URL: https://issues.apache.org/jira/browse/HBASE-13844 > Project: HBase > Issue Type: Improvement >Reporter: Lars George >Assignee: Andy Yang >Priority: Minor > Labels: beginner > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-13844.1.patch, HBASE-13844.2.patch, > HBASE-13844.3.patch, HBASE-13844.branch-2.v0.patch, > HBASE-13844.branch-2.v1.patch, HBASE-13844.branch-2.v2.patch, > HBASE-13844.branch-2.v3.patch, HBASE-13844.branch-2.v4.patch, > HBASE-13844.branch-2.v4.patch, HBASE-13844.branch-2.v5.patch > > > Add KeyValue.parseColumn() to CellUtils (also any other public static helper) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18010) Connect CellChunkMap to be used for flattening in CompactingMemStore
[ https://issues.apache.org/jira/browse/HBASE-18010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187418#comment-16187418 ] Hudson commented on HBASE-18010: FAILURE: Integrated in Jenkins build HBase-2.0 #607 (See [https://builds.apache.org/job/HBase-2.0/607/]) HBASE-18010: CellChunkMap integration into CompactingMemStore, merge to (anastas: rev 445c5bd7b73d2ec73dfb5fbfaeaa2f79d4b7b8c3) * (add) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CellArrayImmutableSegment.java * (add) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CSLMImmutableSegment.java * (add) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CellChunkImmutableSegment.java * (add) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestCompactingToCellFlatMapMemStore.java > Connect CellChunkMap to be used for flattening in CompactingMemStore > > > Key: HBASE-18010 > URL: https://issues.apache.org/jira/browse/HBASE-18010 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Anastasia Braginsky > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18010-branch-2.patch, HBASE-18010-branch-2.patch, > HBASE-18010.branch-2.v1.patch, HBASE-18010.branch-2.v1.patch, > HBASE-18010-branch-2.v2.patch, HBASE-18010-branch-2.v3.patch, > HBASE-18010-V04.patch, HBASE-18010-V06.patch, HBASE-18010-V07.patch, > HBASE-18010-V08.patch, HBASE-18010-V09.patch, HBASE-18010-V10.patch, > HBASE-18010-V11.patch > > > The CellChunkMap helps to create a new type of ImmutableSegment, where the > index (CellSet's delegatee) is going to be CellChunkMap. No big cells or > upserted cells are going to be supported here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18897) Substitute MemStore for Memstore
[ https://issues.apache.org/jira/browse/HBASE-18897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18897: --- Attachment: HBASE-18897.v1.patch v1: more cleanup and rebase > Substitute MemStore for Memstore > > > Key: HBASE-18897 > URL: https://issues.apache.org/jira/browse/HBASE-18897 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0 > > Attachments: HBASE-18897.v0.patch, HBASE-18897.v1.patch > > > Memstore/MemStore is our core component, but we have two ways of writing its > name. We should unify its name in our code base. > Change the both of Class and APIs only. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18897) Substitute MemStore for Memstore
[ https://issues.apache.org/jira/browse/HBASE-18897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18897: --- Status: Patch Available (was: Open) > Substitute MemStore for Memstore > > > Key: HBASE-18897 > URL: https://issues.apache.org/jira/browse/HBASE-18897 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0 > > Attachments: HBASE-18897.v0.patch, HBASE-18897.v1.patch > > > Memstore/MemStore is our core component, but we have two ways of writing its > name. We should unify its name in our code base. > Change the both of Class and APIs only. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18897) Substitute MemStore for Memstore
[ https://issues.apache.org/jira/browse/HBASE-18897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18897: --- Status: Open (was: Patch Available) > Substitute MemStore for Memstore > > > Key: HBASE-18897 > URL: https://issues.apache.org/jira/browse/HBASE-18897 > Project: HBase > Issue Type: Task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0 > > Attachments: HBASE-18897.v0.patch > > > Memstore/MemStore is our core component, but we have two ways of writing its > name. We should unify its name in our code base. > Change the both of Class and APIs only. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18753) Introduce the unsynchronized TimeRangeTracker
[ https://issues.apache.org/jira/browse/HBASE-18753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18753: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Push to branch-2 and master. Thanks for all reviews. > Introduce the unsynchronized TimeRangeTracker > - > > Key: HBASE-18753 > URL: https://issues.apache.org/jira/browse/HBASE-18753 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18753.v0.patch, HBASE-18753.v1.patch, > HBASE-18753.v2.patch, HBASE-18753.v3.patch, HBASE-18753.v4.patch > > > If HBASE-18752 is pushed, it will be better to introduce the unsync > TimeRangeTracker for reducing the cost of recalculation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18010) Connect CellChunkMap to be used for flattening in CompactingMemStore
[ https://issues.apache.org/jira/browse/HBASE-18010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187383#comment-16187383 ] Anastasia Braginsky commented on HBASE-18010: - Sorry, pushed them just now. Thank you so much for your help! > Connect CellChunkMap to be used for flattening in CompactingMemStore > > > Key: HBASE-18010 > URL: https://issues.apache.org/jira/browse/HBASE-18010 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Anastasia Braginsky > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18010-branch-2.patch, HBASE-18010-branch-2.patch, > HBASE-18010.branch-2.v1.patch, HBASE-18010.branch-2.v1.patch, > HBASE-18010-branch-2.v2.patch, HBASE-18010-branch-2.v3.patch, > HBASE-18010-V04.patch, HBASE-18010-V06.patch, HBASE-18010-V07.patch, > HBASE-18010-V08.patch, HBASE-18010-V09.patch, HBASE-18010-V10.patch, > HBASE-18010-V11.patch > > > The CellChunkMap helps to create a new type of ImmutableSegment, where the > index (CellSet's delegatee) is going to be CellChunkMap. No big cells or > upserted cells are going to be supported here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18010) Connect CellChunkMap to be used for flattening in CompactingMemStore
[ https://issues.apache.org/jira/browse/HBASE-18010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187362#comment-16187362 ] Chia-Ping Tsai commented on HBASE-18010: The CSLMImmutableSegment, CellChunkImmutableSegment, and CellArrayImmutableSegment are missed. [~anastas] Would you please push them to branch-2? Thanks. > Connect CellChunkMap to be used for flattening in CompactingMemStore > > > Key: HBASE-18010 > URL: https://issues.apache.org/jira/browse/HBASE-18010 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Anastasia Braginsky > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18010-branch-2.patch, HBASE-18010-branch-2.patch, > HBASE-18010.branch-2.v1.patch, HBASE-18010.branch-2.v1.patch, > HBASE-18010-branch-2.v2.patch, HBASE-18010-branch-2.v3.patch, > HBASE-18010-V04.patch, HBASE-18010-V06.patch, HBASE-18010-V07.patch, > HBASE-18010-V08.patch, HBASE-18010-V09.patch, HBASE-18010-V10.patch, > HBASE-18010-V11.patch > > > The CellChunkMap helps to create a new type of ImmutableSegment, where the > index (CellSet's delegatee) is going to be CellChunkMap. No big cells or > upserted cells are going to be supported here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18753) Introduce the unsynchronized TimeRangeTracker
[ https://issues.apache.org/jira/browse/HBASE-18753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187355#comment-16187355 ] Chia-Ping Tsai commented on HBASE-18753: All are green. Will commit it later. > Introduce the unsynchronized TimeRangeTracker > - > > Key: HBASE-18753 > URL: https://issues.apache.org/jira/browse/HBASE-18753 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18753.v0.patch, HBASE-18753.v1.patch, > HBASE-18753.v2.patch, HBASE-18753.v3.patch, HBASE-18753.v4.patch > > > If HBASE-18752 is pushed, it will be better to introduce the unsync > TimeRangeTracker for reducing the cost of recalculation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18753) Introduce the unsynchronized TimeRangeTracker
[
https://issues.apache.org/jira/browse/HBASE-18753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187354#comment-16187354
]
Hadoop QA commented on HBASE-18753:
---
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
20s{color} | {color:blue} Docker mode activated. {color} |
| {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 7 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
39s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
29s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
20s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
46s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 6m
45s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
5s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
11s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
20s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m
29s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
22s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
50s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
29s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
44m 41s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 4m
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m
0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
19s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 90m
4s{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 6m
50s{color} | {color:green} hbase-mapreduce in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
42s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}176m 36s{color} |
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:5d60123 |
| JIRA Issue | HBASE-18753 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12889880/HBASE-18753.v4.patch |
| Optional Tests | asflicense shadedjars javac javadoc unit findbugs
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 2acf18f6a3b1 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
[jira] [Commented] (HBASE-18703) Inconsistent behavior for preBatchMutate in doMiniBatchMutate and processRowsWithLocks
[
https://issues.apache.org/jira/browse/HBASE-18703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187340#comment-16187340
]
Hadoop QA commented on HBASE-18703:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
21s{color} | {color:blue} Docker mode activated. {color} |
| {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:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 3 new or modified test
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
29s{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
52s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
56s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
26s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 5m
16s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
53s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
43s{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m
17s{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
0s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
53s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
41s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
24s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
55s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
36m 9s{color} | {color:green} Patch does not cause any errors with Hadoop
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha4. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
9s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m
17s{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:red}-1{color} | {color:red} unit {color} | {color:red} 98m 39s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
28s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}159m 45s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestFromClientSide3 |
| | hadoop.hbase.client.TestCheckAndMutate |
| | hadoop.hbase.util.TestFromClientSide3WoUnsafe |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:5d60123 |
| JIRA Issue | HBASE-18703 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12889878/hbase-18703.master.004.patch
|
| Optional Tests | asflicense shadedjars javac javadoc unit findbugs
hadoopcheck hbaseanti checkstyle compile |
| uname | Linux b2c8487c1d17 3.13.0-119-generic #166-Ubuntu SMP Wed May 3
12:18:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
|
[jira] [Commented] (HBASE-18913) TestShell fails because NoMethodError: undefined method parseColumn
[ https://issues.apache.org/jira/browse/HBASE-18913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187332#comment-16187332 ] Chia-Ping Tsai commented on HBASE-18913: bq. That is caused by HBASE-13844. I will push a addendum to fix it. done > TestShell fails because NoMethodError: undefined method parseColumn > --- > > Key: HBASE-18913 > URL: https://issues.apache.org/jira/browse/HBASE-18913 > Project: HBase > Issue Type: Bug > Components: shell >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18913.patch > > > Error: > ^[[48;5;16;38;5;226;1mtest_truncate_preserve_should_empty_a_table(Hbase::AdminMethodsTest)^[[0m: > NoMethodError: undefined method `parseColumn' for > Java::OrgApacheHadoopHbase::KeyValue:Class > org/jruby/RubyBasicObject.java:1653:in `method_missing' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:725:in > `parse_column_name' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:131:in > `_put_internal' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands/put.rb:49:in > `put' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:38:in > `block in command_safe' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:108:in > `translate_hbase_exceptions' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:38:in > `command_safe' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell.rb:155:in > `internal_command' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:47:in > `block in put' > src/test/ruby/hbase/admin_test.rb:291:in `block in > test_truncate_preserve_should_empty_a_table' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-13844) Move static helper methods from KeyValue into CellUtils
[
https://issues.apache.org/jira/browse/HBASE-13844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187331#comment-16187331
]
Chia-Ping Tsai commented on HBASE-13844:
HBASE-18913 reports a shell error.
{code}
/testptch/hbase/hbase-shell/src/main/ruby/hbase/table.rb:E:751:10: undefined
method org
{code}
Will push an addeneum to fix it.
> Move static helper methods from KeyValue into CellUtils
> ---
>
> Key: HBASE-13844
> URL: https://issues.apache.org/jira/browse/HBASE-13844
> Project: HBase
> Issue Type: Improvement
>Reporter: Lars George
>Assignee: Andy Yang
>Priority: Minor
> Labels: beginner
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-13844.1.patch, HBASE-13844.2.patch,
> HBASE-13844.3.patch, HBASE-13844.branch-2.v0.patch,
> HBASE-13844.branch-2.v1.patch, HBASE-13844.branch-2.v2.patch,
> HBASE-13844.branch-2.v3.patch, HBASE-13844.branch-2.v4.patch,
> HBASE-13844.branch-2.v4.patch, HBASE-13844.branch-2.v5.patch
>
>
> Add KeyValue.parseColumn() to CellUtils (also any other public static helper)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (HBASE-18913) TestShell fails because NoMethodError: undefined method parseColumn
[ https://issues.apache.org/jira/browse/HBASE-18913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187327#comment-16187327 ] Chia-Ping Tsai commented on HBASE-18913: bq. /testptch/hbase/hbase-shell/src/main/ruby/hbase/table.rb:E:751:10: undefined method org That is caused by HBASE-13844. I will push a addendum to fix it. > TestShell fails because NoMethodError: undefined method parseColumn > --- > > Key: HBASE-18913 > URL: https://issues.apache.org/jira/browse/HBASE-18913 > Project: HBase > Issue Type: Bug > Components: shell >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18913.patch > > > Error: > ^[[48;5;16;38;5;226;1mtest_truncate_preserve_should_empty_a_table(Hbase::AdminMethodsTest)^[[0m: > NoMethodError: undefined method `parseColumn' for > Java::OrgApacheHadoopHbase::KeyValue:Class > org/jruby/RubyBasicObject.java:1653:in `method_missing' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:725:in > `parse_column_name' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:131:in > `_put_internal' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands/put.rb:49:in > `put' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:38:in > `block in command_safe' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:108:in > `translate_hbase_exceptions' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:38:in > `command_safe' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell.rb:155:in > `internal_command' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:47:in > `block in put' > src/test/ruby/hbase/admin_test.rb:291:in `block in > test_truncate_preserve_should_empty_a_table' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18409) Migrate Client Metrics from codahale to hbase-metrics
[
https://issues.apache.org/jira/browse/HBASE-18409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187325#comment-16187325
]
Hadoop QA commented on HBASE-18409:
---
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 5s{color}
| {color:red} HBASE-18409 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.4.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-18409 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12889881/0003-HBASE-18409-MetricsConnection-client-metrics-migration.patch
|
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/8887/console |
| Powered by | Apache Yetus 0.4.0 http://yetus.apache.org |
This message was automatically generated.
> Migrate Client Metrics from codahale to hbase-metrics
> -
>
> Key: HBASE-18409
> URL: https://issues.apache.org/jira/browse/HBASE-18409
> Project: HBase
> Issue Type: Improvement
> Components: Client, java, metrics
>Affects Versions: 3.0.0
>Reporter: Ronald Macmaster
> Labels: newbie
> Fix For: 3.0.0
>
> Attachments:
> 0001-HBASE-18409-MetricsConnection-client-metrics-migration.patch,
> 0002-HBASE-18409-MetricsConnection-client-metrics-migrati.patch,
> 0003-HBASE-18409-MetricsConnection-client-metrics-migration.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> Currently, the metrics for hbase-client are tailored for reporting via a
> client-side JMX server.
> The MetricsConnection handles the metrics management and reporting via the
> metrics platform from codahale.
> This approach worked well for hbase-1.3.1 when the metrics platform was still
> relatively young, but it could be improved by using the new
> hbase-metrics-api.
> Now that we have an actual hbase-metrics-api that master, regionserver,
> zookeeper, and other daemons use, it would be good to also allow the client
> to leverage the metrics-api.
> Then, the client could also report its metrics via Hadoop's metrics2 if
> desired or through another platform that utilizes the hbase-metrics-api.
> If left alone, client metrics will continue to be only barely visible through
> a client-side JMX server.
> The migration to the new metrics-api could be done by simply changing the
> Metrics data types from codahale types to hbase-metrics types without
> changing the metrics signatures of MetricsConnection unless completely
> necessary.
> The codahale MetricsRegistry would also have to be exchanged for a
> hbase-metrics MetricsRegistry.
> I found this to be a necessary change after attempting to implement my own
> Reporter to use within the MetricsConnection class.
> I was attempting to create a HadoopMetrics2Reporter that extends the codahale
> ScheduledReporter and reports the MetricsConnection metrics to Hadoop's
> metrics2 system.
> The already existing infrastructure in the hbase-metrics and
> hbase-metrics-api projects could be easily leveraged for a cleaner solution.
> If completed successfully, users could instead access their client-side
> metrics through the hbase-metrics-api.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18913) TestShell fails because NoMethodError: undefined method parseColumn
[ https://issues.apache.org/jira/browse/HBASE-18913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18913: --- Component/s: shell > TestShell fails because NoMethodError: undefined method parseColumn > --- > > Key: HBASE-18913 > URL: https://issues.apache.org/jira/browse/HBASE-18913 > Project: HBase > Issue Type: Bug > Components: shell >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18913.patch > > > Error: > ^[[48;5;16;38;5;226;1mtest_truncate_preserve_should_empty_a_table(Hbase::AdminMethodsTest)^[[0m: > NoMethodError: undefined method `parseColumn' for > Java::OrgApacheHadoopHbase::KeyValue:Class > org/jruby/RubyBasicObject.java:1653:in `method_missing' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:725:in > `parse_column_name' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:131:in > `_put_internal' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands/put.rb:49:in > `put' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:38:in > `block in command_safe' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:108:in > `translate_hbase_exceptions' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:38:in > `command_safe' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell.rb:155:in > `internal_command' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:47:in > `block in put' > src/test/ruby/hbase/admin_test.rb:291:in `block in > test_truncate_preserve_should_empty_a_table' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18913) TestShell fails because NoMethodError: undefined method parseColumn
[ https://issues.apache.org/jira/browse/HBASE-18913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18913: --- Fix Version/s: 2.0.0-beta-1 > TestShell fails because NoMethodError: undefined method parseColumn > --- > > Key: HBASE-18913 > URL: https://issues.apache.org/jira/browse/HBASE-18913 > Project: HBase > Issue Type: Bug > Components: shell >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18913.patch > > > Error: > ^[[48;5;16;38;5;226;1mtest_truncate_preserve_should_empty_a_table(Hbase::AdminMethodsTest)^[[0m: > NoMethodError: undefined method `parseColumn' for > Java::OrgApacheHadoopHbase::KeyValue:Class > org/jruby/RubyBasicObject.java:1653:in `method_missing' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:725:in > `parse_column_name' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:131:in > `_put_internal' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands/put.rb:49:in > `put' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:38:in > `block in command_safe' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:108:in > `translate_hbase_exceptions' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:38:in > `command_safe' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell.rb:155:in > `internal_command' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:47:in > `block in put' > src/test/ruby/hbase/admin_test.rb:291:in `block in > test_truncate_preserve_should_empty_a_table' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18913) TestShell fails because NoMethodError: undefined method parseColumn
[ https://issues.apache.org/jira/browse/HBASE-18913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187324#comment-16187324 ] Chia-Ping Tsai commented on HBASE-18913: +1. Nice finding...That is my fault. :( > TestShell fails because NoMethodError: undefined method parseColumn > --- > > Key: HBASE-18913 > URL: https://issues.apache.org/jira/browse/HBASE-18913 > Project: HBase > Issue Type: Bug > Components: shell >Reporter: Guanghao Zhang >Assignee: Guanghao Zhang > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18913.patch > > > Error: > ^[[48;5;16;38;5;226;1mtest_truncate_preserve_should_empty_a_table(Hbase::AdminMethodsTest)^[[0m: > NoMethodError: undefined method `parseColumn' for > Java::OrgApacheHadoopHbase::KeyValue:Class > org/jruby/RubyBasicObject.java:1653:in `method_missing' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:725:in > `parse_column_name' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:131:in > `_put_internal' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands/put.rb:49:in > `put' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:38:in > `block in command_safe' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:108:in > `translate_hbase_exceptions' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell/commands.rb:38:in > `command_safe' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/shell.rb:155:in > `internal_command' > /home/hao/open_source/hbase/hbase-shell/src/main/ruby/hbase/table.rb:47:in > `block in put' > src/test/ruby/hbase/admin_test.rb:291:in `block in > test_truncate_preserve_should_empty_a_table' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18409) Migrate Client Metrics from codahale to hbase-metrics
[ https://issues.apache.org/jira/browse/HBASE-18409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ronald Macmaster updated HBASE-18409: - Attachment: 0003-HBASE-18409-MetricsConnection-client-metrics-migration.patch Revised to include the hedgedReads and concurrentServerCalls. Also incorporates the edits suggested by Josh Elser. > Migrate Client Metrics from codahale to hbase-metrics > - > > Key: HBASE-18409 > URL: https://issues.apache.org/jira/browse/HBASE-18409 > Project: HBase > Issue Type: Improvement > Components: Client, java, metrics >Affects Versions: 3.0.0 >Reporter: Ronald Macmaster > Labels: newbie > Fix For: 3.0.0 > > Attachments: > 0001-HBASE-18409-MetricsConnection-client-metrics-migration.patch, > 0002-HBASE-18409-MetricsConnection-client-metrics-migrati.patch, > 0003-HBASE-18409-MetricsConnection-client-metrics-migration.patch > > Original Estimate: 168h > Remaining Estimate: 168h > > Currently, the metrics for hbase-client are tailored for reporting via a > client-side JMX server. > The MetricsConnection handles the metrics management and reporting via the > metrics platform from codahale. > This approach worked well for hbase-1.3.1 when the metrics platform was still > relatively young, but it could be improved by using the new > hbase-metrics-api. > Now that we have an actual hbase-metrics-api that master, regionserver, > zookeeper, and other daemons use, it would be good to also allow the client > to leverage the metrics-api. > Then, the client could also report its metrics via Hadoop's metrics2 if > desired or through another platform that utilizes the hbase-metrics-api. > If left alone, client metrics will continue to be only barely visible through > a client-side JMX server. > The migration to the new metrics-api could be done by simply changing the > Metrics data types from codahale types to hbase-metrics types without > changing the metrics signatures of MetricsConnection unless completely > necessary. > The codahale MetricsRegistry would also have to be exchanged for a > hbase-metrics MetricsRegistry. > I found this to be a necessary change after attempting to implement my own > Reporter to use within the MetricsConnection class. > I was attempting to create a HadoopMetrics2Reporter that extends the codahale > ScheduledReporter and reports the MetricsConnection metrics to Hadoop's > metrics2 system. > The already existing infrastructure in the hbase-metrics and > hbase-metrics-api projects could be easily leveraged for a cleaner solution. > If completed successfully, users could instead access their client-side > metrics through the hbase-metrics-api. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18010) Connect CellChunkMap to be used for flattening in CompactingMemStore
[ https://issues.apache.org/jira/browse/HBASE-18010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18010: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) > Connect CellChunkMap to be used for flattening in CompactingMemStore > > > Key: HBASE-18010 > URL: https://issues.apache.org/jira/browse/HBASE-18010 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Anastasia Braginsky > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18010-branch-2.patch, HBASE-18010-branch-2.patch, > HBASE-18010.branch-2.v1.patch, HBASE-18010.branch-2.v1.patch, > HBASE-18010-branch-2.v2.patch, HBASE-18010-branch-2.v3.patch, > HBASE-18010-V04.patch, HBASE-18010-V06.patch, HBASE-18010-V07.patch, > HBASE-18010-V08.patch, HBASE-18010-V09.patch, HBASE-18010-V10.patch, > HBASE-18010-V11.patch > > > The CellChunkMap helps to create a new type of ImmutableSegment, where the > index (CellSet's delegatee) is going to be CellChunkMap. No big cells or > upserted cells are going to be supported here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18010) Connect CellChunkMap to be used for flattening in CompactingMemStore
[ https://issues.apache.org/jira/browse/HBASE-18010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187322#comment-16187322 ] Hudson commented on HBASE-18010: FAILURE: Integrated in Jenkins build HBase-2.0 #606 (See [https://builds.apache.org/job/HBase-2.0/606/]) HBASE-18010: CellChunkMap integration into CompactingMemStore, merge to (anastas: rev 95405fbd83e45e22f8608ff7966cb05fd1103729) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompactionPipeline.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreLABImpl.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestWalAndCompactingMemStoreFlush.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/io/TestHeapSize.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegionReplayEvents.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompositeImmutableSegment.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/Segment.java * (delete) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestCompactingToCellArrayMapMemStore.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreLAB.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestPerColumnFamilyFlush.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ImmutableMemStoreLAB.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MutableSegment.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestCellFlatSet.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ChunkCreator.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/MemStoreCompactor.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CompactingMemStore.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/SegmentFactory.java * (edit) hbase-common/src/main/java/org/apache/hadoop/hbase/util/ClassSize.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/ImmutableSegment.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHStore.java * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/CellChunkMap.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestCompactingMemStore.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestDefaultMemStore.java > Connect CellChunkMap to be used for flattening in CompactingMemStore > > > Key: HBASE-18010 > URL: https://issues.apache.org/jira/browse/HBASE-18010 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Anastasia Braginsky > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18010-branch-2.patch, HBASE-18010-branch-2.patch, > HBASE-18010.branch-2.v1.patch, HBASE-18010.branch-2.v1.patch, > HBASE-18010-branch-2.v2.patch, HBASE-18010-branch-2.v3.patch, > HBASE-18010-V04.patch, HBASE-18010-V06.patch, HBASE-18010-V07.patch, > HBASE-18010-V08.patch, HBASE-18010-V09.patch, HBASE-18010-V10.patch, > HBASE-18010-V11.patch > > > The CellChunkMap helps to create a new type of ImmutableSegment, where the > index (CellSet's delegatee) is going to be CellChunkMap. No big cells or > upserted cells are going to be supported here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18920) Operation.toString() is counterintuitive
[
https://issues.apache.org/jira/browse/HBASE-18920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187321#comment-16187321
]
Chia-Ping Tsai commented on HBASE-18920:
{quote}
Indicate that there are more column qualifiers projected when you've truncated
the toString() based on the max number to display. Something simple like adding
a "..." to the string would be fine.
Increasing the default value to something like 20 or 30. That won't be an issue
memory-wise, but will handle more cases out of the box.
{quote}
+1. Do you start the patch?
> Operation.toString() is counterintuitive
>
>
> Key: HBASE-18920
> URL: https://issues.apache.org/jira/browse/HBASE-18920
> Project: HBase
> Issue Type: Bug
>Reporter: James Taylor
>
> When debugging, you often need to know which columns are projected into the
> Scan. The Operation.toString() silently truncates what you see to the first
> 5. Typically, if you truncate a value, you should end it with "..." so that
> the user knows there are actually more (instead of wasting time thinking
> they're not projecting everything that needs to be projected). Also, a limit
> of 5 is way to small of a default.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (HBASE-18753) Introduce the unsynchronized TimeRangeTracker
[ https://issues.apache.org/jira/browse/HBASE-18753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18753: --- Status: Patch Available (was: Open) > Introduce the unsynchronized TimeRangeTracker > - > > Key: HBASE-18753 > URL: https://issues.apache.org/jira/browse/HBASE-18753 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18753.v0.patch, HBASE-18753.v1.patch, > HBASE-18753.v2.patch, HBASE-18753.v3.patch, HBASE-18753.v4.patch > > > If HBASE-18752 is pushed, it will be better to introduce the unsync > TimeRangeTracker for reducing the cost of recalculation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18753) Introduce the unsynchronized TimeRangeTracker
[ https://issues.apache.org/jira/browse/HBASE-18753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18753: --- Status: Open (was: Patch Available) > Introduce the unsynchronized TimeRangeTracker > - > > Key: HBASE-18753 > URL: https://issues.apache.org/jira/browse/HBASE-18753 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18753.v0.patch, HBASE-18753.v1.patch, > HBASE-18753.v2.patch, HBASE-18753.v3.patch, HBASE-18753.v4.patch > > > If HBASE-18752 is pushed, it will be better to introduce the unsync > TimeRangeTracker for reducing the cost of recalculation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18753) Introduce the unsynchronized TimeRangeTracker
[ https://issues.apache.org/jira/browse/HBASE-18753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai updated HBASE-18753: --- Attachment: HBASE-18753.v4.patch v4: rebase > Introduce the unsynchronized TimeRangeTracker > - > > Key: HBASE-18753 > URL: https://issues.apache.org/jira/browse/HBASE-18753 > Project: HBase > Issue Type: Sub-task >Reporter: Chia-Ping Tsai >Assignee: Chia-Ping Tsai > Fix For: 2.0.0-beta-1 > > Attachments: HBASE-18753.v0.patch, HBASE-18753.v1.patch, > HBASE-18753.v2.patch, HBASE-18753.v3.patch, HBASE-18753.v4.patch > > > If HBASE-18752 is pushed, it will be better to introduce the unsync > TimeRangeTracker for reducing the cost of recalculation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (HBASE-18703) Inconsistent behavior for preBatchMutate in doMiniBatchMutate and processRowsWithLocks
[ https://issues.apache.org/jira/browse/HBASE-18703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Umesh Agashe updated HBASE-18703: - Attachment: hbase-18703.master.004.patch > Inconsistent behavior for preBatchMutate in doMiniBatchMutate and > processRowsWithLocks > -- > > Key: HBASE-18703 > URL: https://issues.apache.org/jira/browse/HBASE-18703 > Project: HBase > Issue Type: Sub-task > Components: Coprocessors >Reporter: Duo Zhang >Assignee: Umesh Agashe >Priority: Critical > Fix For: 2.0.0-alpha-4 > > Attachments: hbase-18703.master.001.patch, > hbase-18703.master.002.patch, hbase-18703.master.003.patch, > hbase-18703.master.004.patch > > > In doMiniBatchMutate, the preBatchMutate is called before building WAL, but > in processRowsWithLocks, we suggest the RowProcessor implementation to build > WAL in process method, which is ahead of preBatchMutate. > If a CP modifies the mutations, especially if it removes some cells from the > mutations, then the behavior of processRowsWithLocks is broken. The changes > applied to memstore and WAL will be different. And there is no way to remove > entries from a WALEdit through CP. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18010) Connect CellChunkMap to be used for flattening in CompactingMemStore
[ https://issues.apache.org/jira/browse/HBASE-18010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187307#comment-16187307 ] Anastasia Braginsky commented on HBASE-18010: - Committing to Release 2.0, unless any objection will be shown soon > Connect CellChunkMap to be used for flattening in CompactingMemStore > > > Key: HBASE-18010 > URL: https://issues.apache.org/jira/browse/HBASE-18010 > Project: HBase > Issue Type: Sub-task >Reporter: Anastasia Braginsky >Assignee: Anastasia Braginsky > Fix For: 2.0.0, 3.0.0 > > Attachments: HBASE-18010-branch-2.patch, HBASE-18010-branch-2.patch, > HBASE-18010.branch-2.v1.patch, HBASE-18010.branch-2.v1.patch, > HBASE-18010-branch-2.v2.patch, HBASE-18010-branch-2.v3.patch, > HBASE-18010-V04.patch, HBASE-18010-V06.patch, HBASE-18010-V07.patch, > HBASE-18010-V08.patch, HBASE-18010-V09.patch, HBASE-18010-V10.patch, > HBASE-18010-V11.patch > > > The CellChunkMap helps to create a new type of ImmutableSegment, where the > index (CellSet's delegatee) is going to be CellChunkMap. No big cells or > upserted cells are going to be supported here. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (HBASE-18920) Operation.toString() is counterintuitive
[ https://issues.apache.org/jira/browse/HBASE-18920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16187290#comment-16187290 ] James Taylor commented on HBASE-18920: -- IMHO, there are two changes needed: - Indicate that there are more column qualifiers projected when you've truncated the toString() based on the max number to display. Something simple like adding a "..." to the string would be fine. - Increasing the default value to something like 20 or 30. That won't be an issue memory-wise, but will handle more cases out of the box. - Making it configurable would be nice, but there are so many dials and knobs, it's unlikely someone will modify it. I just filed it because I spent a fair amount of time debugging a non issue, thinking Phoenix wasn't projecting all the expected column qualifiers (and I'd rather save others this pain). > Operation.toString() is counterintuitive > > > Key: HBASE-18920 > URL: https://issues.apache.org/jira/browse/HBASE-18920 > Project: HBase > Issue Type: Bug >Reporter: James Taylor > > When debugging, you often need to know which columns are projected into the > Scan. The Operation.toString() silently truncates what you see to the first > 5. Typically, if you truncate a value, you should end it with "..." so that > the user knows there are actually more (instead of wasting time thinking > they're not projecting everything that needs to be projected). Also, a limit > of 5 is way to small of a default. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
