[
https://issues.apache.org/jira/browse/HBASE-29004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914796#comment-17914796
]
Hudson commented on HBASE-29004:
--------------------------------
Results for branch branch-2
[build #1225 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1225/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1225/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/1225/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/1225/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1225/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/1225/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk17 hadoop ${HADOOP_THREE_VERSION} backward compatibility
checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1225/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk17 hadoop ${HADOOP_THREE_VERSION} backward compatibility
checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1225/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk17 hadoop ${HADOOP_THREE_VERSION} backward compatibility
checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1225/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 source release artifact{color}
-- Something went wrong with this stage, [check relevant console
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1225//console].
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2/1225//console].
> Optimize unnecessary type castings in Scan and Get setter methods
> -----------------------------------------------------------------
>
> Key: HBASE-29004
> URL: https://issues.apache.org/jira/browse/HBASE-29004
> Project: HBase
> Issue Type: Improvement
> Components: Performance
> Reporter: Chandra Sekhar K
> Assignee: Chandra Sekhar K
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.5.11, 2.6.2
>
>
> In the setter methods of Scan and Get, we invoke the super class method, type
> cast and return the object.
> {code:java}
> public Scan setColumnFamilyTimeRange(byte[] cf, long minStamp, long maxStamp)
> {
> return (Scan) super.setColumnFamilyTimeRange(cf, minStamp, maxStamp);
> }{code}
>
> In profiler reports it's observed that this typecasting does take some
> additional cpu cycles. we can optimize this by adding an explicit return
> statement with current object.
> {code:java}
> public Scan setColumnFamilyTimeRange(byte[] cf, long minStamp, long maxStamp)
> {
> super.setColumnFamilyTimeRange(cf, minStamp, maxStamp);
> return this;
> }{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
