Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 12 Sep 2017 09:07:00 +0000 (UTC)
From: "Xiang Li (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12951438.1458274728000.88999.1505207220199@Atlassian.JIRA>
In-Reply-To: <JIRA.12951438.1458274728000@Atlassian.JIRA>
References: <JIRA.12951438.1458274728000@Atlassian.JIRA> <JIRA.12951438.1458274728506@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-15482) Provide an option to skip
 calculating block locations for SnapshotInputFormat
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 12 Sep 2017 09:07:05 -0000


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

Xiang Li commented on HBASE-15482:
----------------------------------

Hi, this JIRA is still valid now? I plan to work on it if it is still valid.

> Provide an option to skip calculating block locations for SnapshotInputFormat
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-15482
>                 URL: https://issues.apache.org/jira/browse/HBASE-15482
>             Project: HBase
>          Issue Type: Improvement
>          Components: mapreduce
>            Reporter: Liyin Tang
>            Priority: Minor
>
> When a MR job is reading from SnapshotInputFormat, it needs to calculate the splits based on the block locations in order to get best locality. However, this process may take a long time for large snapshots. 
> In some setup, the computing layer, Spark, Hive or Presto could run out side of HBase cluster. In these scenarios, the block locality doesn't matter. Therefore, it will be great to have an option to skip calculating the block locations for every job. That will super useful for the Hive/Presto/Spark connectors.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)