[jira] [Commented] (HBASE-24500) The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
[
https://issues.apache.org/jira/browse/HBASE-24500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127181#comment-17127181
]
Hudson commented on HBASE-24500:
Results for branch branch-2.2
[build #886 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/886/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/886//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/886//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/886//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
> ---
>
> Key: HBASE-24500
> URL: https://issues.apache.org/jira/browse/HBASE-24500
> Project: HBase
> Issue Type: Task
> Components: Client, read replicas
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> In this method, we will copy all the fields, including RegionName and
> EncodedRegionName of the RegionInfo, so after we changed some other fields
> like start key or stop key or replica id, and then create a new RegionInfo,
> the RegionName of the RegionInfo will not be regenerated and cause problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24500) The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
[
https://issues.apache.org/jira/browse/HBASE-24500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127208#comment-17127208
]
Hudson commented on HBASE-24500:
Results for branch branch-2
[build #2692 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2692/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2692/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2692/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2692/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2692/JDK11_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}
> The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
> ---
>
> Key: HBASE-24500
> URL: https://issues.apache.org/jira/browse/HBASE-24500
> Project: HBase
> Issue Type: Task
> Components: Client, read replicas
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> In this method, we will copy all the fields, including RegionName and
> EncodedRegionName of the RegionInfo, so after we changed some other fields
> like start key or stop key or replica id, and then create a new RegionInfo,
> the RegionName of the RegionInfo will not be regenerated and cause problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24500) The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
[
https://issues.apache.org/jira/browse/HBASE-24500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126912#comment-17126912
]
Hudson commented on HBASE-24500:
Results for branch master
[build #1748 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1748/]: (/)
*{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1748/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1600//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1748/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1748/JDK11_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}
> The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
> ---
>
> Key: HBASE-24500
> URL: https://issues.apache.org/jira/browse/HBASE-24500
> Project: HBase
> Issue Type: Task
> Components: Client, read replicas
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> In this method, we will copy all the fields, including RegionName and
> EncodedRegionName of the RegionInfo, so after we changed some other fields
> like start key or stop key or replica id, and then create a new RegionInfo,
> the RegionName of the RegionInfo will not be regenerated and cause problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24500) The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
[
https://issues.apache.org/jira/browse/HBASE-24500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126831#comment-17126831
]
Hudson commented on HBASE-24500:
Results for branch branch-2.3
[build #123 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/123/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/123/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/123/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/123/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/123/JDK11_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}
> The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
> ---
>
> Key: HBASE-24500
> URL: https://issues.apache.org/jira/browse/HBASE-24500
> Project: HBase
> Issue Type: Task
> Components: Client, read replicas
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> In this method, we will copy all the fields, including RegionName and
> EncodedRegionName of the RegionInfo, so after we changed some other fields
> like start key or stop key or replica id, and then create a new RegionInfo,
> the RegionName of the RegionInfo will not be regenerated and cause problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24500) The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
[
https://issues.apache.org/jira/browse/HBASE-24500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126315#comment-17126315
]
Hudson commented on HBASE-24500:
Results for branch branch-2
[build #2691 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2691/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2691/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2691/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2691/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2691/JDK11_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}
> The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
> ---
>
> Key: HBASE-24500
> URL: https://issues.apache.org/jira/browse/HBASE-24500
> Project: HBase
> Issue Type: Task
> Components: Client, read replicas
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> In this method, we will copy all the fields, including RegionName and
> EncodedRegionName of the RegionInfo, so after we changed some other fields
> like start key or stop key or replica id, and then create a new RegionInfo,
> the RegionName of the RegionInfo will not be regenerated and cause problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24500) The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
[
https://issues.apache.org/jira/browse/HBASE-24500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126113#comment-17126113
]
Hudson commented on HBASE-24500:
Results for branch master
[build #1747 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1747/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1747/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1600//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1747/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/master/1747//console].
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
> ---
>
> Key: HBASE-24500
> URL: https://issues.apache.org/jira/browse/HBASE-24500
> Project: HBase
> Issue Type: Task
> Components: Client, read replicas
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> In this method, we will copy all the fields, including RegionName and
> EncodedRegionName of the RegionInfo, so after we changed some other fields
> like start key or stop key or replica id, and then create a new RegionInfo,
> the RegionName of the RegionInfo will not be regenerated and cause problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24500) The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
[
https://issues.apache.org/jira/browse/HBASE-24500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126091#comment-17126091
]
Hudson commented on HBASE-24500:
Results for branch branch-2.3
[build #122 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/122/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/122/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/122/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/122/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/122/JDK11_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}
> The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
> ---
>
> Key: HBASE-24500
> URL: https://issues.apache.org/jira/browse/HBASE-24500
> Project: HBase
> Issue Type: Task
> Components: Client, read replicas
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Blocker
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6
>
>
> In this method, we will copy all the fields, including RegionName and
> EncodedRegionName of the RegionInfo, so after we changed some other fields
> like start key or stop key or replica id, and then create a new RegionInfo,
> the RegionName of the RegionInfo will not be regenerated and cause problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24500) The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
[ https://issues.apache.org/jira/browse/HBASE-24500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125531#comment-17125531 ] Duo Zhang commented on HBASE-24500: --- Revert from branch-2.3+. Will open a new PR once the question on HBASE-23313 has been resolved. > The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange > --- > > Key: HBASE-24500 > URL: https://issues.apache.org/jira/browse/HBASE-24500 > Project: HBase > Issue Type: Task > Components: Client, read replicas >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Blocker > Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6 > > > In this method, we will copy all the fields, including RegionName and > EncodedRegionName of the RegionInfo, so after we changed some other fields > like start key or stop key or replica id, and then create a new RegionInfo, > the RegionName of the RegionInfo will not be regenerated and cause problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24500) The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
[ https://issues.apache.org/jira/browse/HBASE-24500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125526#comment-17125526 ] Duo Zhang commented on HBASE-24500: --- Oh shit, seems we use the ProtobufUtil.toProtoRegionInfo in HBCK2, let me check. > The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange > --- > > Key: HBASE-24500 > URL: https://issues.apache.org/jira/browse/HBASE-24500 > Project: HBase > Issue Type: Task > Components: Client, read replicas >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Critical > Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6 > > > In this method, we will copy all the fields, including RegionName and > EncodedRegionName of the RegionInfo, so after we changed some other fields > like start key or stop key or replica id, and then create a new RegionInfo, > the RegionName of the RegionInfo will not be regenerated and cause problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24500) The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange
[ https://issues.apache.org/jira/browse/HBASE-24500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125523#comment-17125523 ] Duo Zhang commented on HBASE-24500: --- oh, wait a minute, we do not have encoded name for RegionInfo proto on branch-2.2. Let me check when we introduced this field in proto. > The behavior of RegionInfoBuilder.newBuilder(RegionInfo) is strange > --- > > Key: HBASE-24500 > URL: https://issues.apache.org/jira/browse/HBASE-24500 > Project: HBase > Issue Type: Task > Components: Client, read replicas >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Critical > Fix For: 3.0.0-alpha-1, 2.3.0, 2.2.6 > > > In this method, we will copy all the fields, including RegionName and > EncodedRegionName of the RegionInfo, so after we changed some other fields > like start key or stop key or replica id, and then create a new RegionInfo, > the RegionName of the RegionInfo will not be regenerated and cause problem. -- This message was sent by Atlassian Jira (v8.3.4#803005)
