[
https://issues.apache.org/jira/browse/HBASE-28862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888716#comment-17888716
]
Hudson commented on HBASE-28862:
--------------------------------
Results for branch branch-3
[build #309 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/309/]:
(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-3/309/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/309/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{color}
> Change the generic type for ObserverContext from
> 'RegionCoprocessorEnvironment' to '? extends RegionCoprocessorEnvironment' in
> RegionObserver
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-28862
> URL: https://issues.apache.org/jira/browse/HBASE-28862
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors, regionserver
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.0.0-beta-2
>
>
> This will be a breaking change for coprocessor implementation, but the
> ability of region observer is not changed, so I think it is OK to include
> this in 3.0.0 release, as we have already changed the coprocessor protobuf to
> the relocated one, which already breaks lots of coprocessors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
