[
https://issues.apache.org/jira/browse/HBASE-26255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413338#comment-17413338
]
Hudson commented on HBASE-26255:
--------------------------------
Results for branch branch-2
[build #342 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/342/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/342/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/342/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/342/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/342/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}
> Add an option to use region location from meta table in
> TableSnapshotInputFormat
> --------------------------------------------------------------------------------
>
> Key: HBASE-26255
> URL: https://issues.apache.org/jira/browse/HBASE-26255
> Project: HBase
> Issue Type: Improvement
> Components: mapreduce
> Affects Versions: 2.3.6
> Reporter: Huaxiang Sun
> Assignee: Huaxiang Sun
> Priority: Major
> Fix For: 3.0.0-alpha-2, 2.3.7, 2.4.7
>
>
> TableSnapshotInputFormat currently calculates block locality of a region to
> decide the best location to run the task. While this works for a small scale
> table snapshot, we found that for a table snapshot with many regions, the
> locality calculation takes too much time.
> In the case of a table with high locality, we can use region location from
> meta table to decide a snapshot region's location. Add an option to support
> it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
