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

Hudson commented on HBASE-29528:
--------------------------------

Results for branch branch-2.6
        [build #350 on 
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/350/]:
 (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/350/General_20Nightly_20Build_20Report/]


(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/350/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/350/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/350/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/350/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop 3.3.5 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/350/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk17 hadoop 3.3.6 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/350/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(x) {color:red}-1 jdk17 hadoop 3.4.0 backward compatibility checks{color}
-- For more information [see jdk17 
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.6/350/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test for HBase 2 {color}
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.1 {color}


> Support for cellVisibility in Thrift interface
> ----------------------------------------------
>
>                 Key: HBASE-29528
>                 URL: https://issues.apache.org/jira/browse/HBASE-29528
>             Project: HBase
>          Issue Type: Improvement
>          Components: Thrift
>            Reporter: Adam Sjøgren
>            Assignee: Adam Sjøgren
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.7.0, 3.0.0-beta-2, 2.6.4
>
>         Attachments: 
> 0001-HBASE-29528-Support-cellVisility-in-Thrift-interface.patch, 
> hbase-thrift-cellvisibility.patch
>
>
> A colleague of mine added support for cellVisibility to the Thrift interface 
> in HBase, to allow deleting cells with visibility labels applied, via Thrift.
> We have been using this patch internally since 2019 with HBase 2.2.2, 2.5.6, 
> and 2.5.8 (currently working on compiling 2.5.12).
> It is a small change:
> {noformat}
>  
> hbase-thrift/src/main/java/org/apache/hadoop/hbase/thrift2/ThriftUtilities.java
>                        |  4 +++
>  hbase-thrift/src/main/resources/org/apache/hadoop/hbase/thrift2/hbase.thrift 
>                          |  3 +-
>  
> .../src/test/java/org/apache/hadoop/hbase/thrift2/TestThriftHBaseServiceHandlerWithLabels.java
>         | 93 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 99 insertions(+), 1 deletion(-) {noformat}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to