From issues-return-329293-archive-asf-public=cust-asf.ponee.io@hbase.apache.org Thu Jan 11 20:17:12 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 9CC09180656 for ; Thu, 11 Jan 2018 20:17:12 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8C710160C23; Thu, 11 Jan 2018 19:17:12 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D2429160C13 for ; Thu, 11 Jan 2018 20:17:11 +0100 (CET) Received: (qmail 13302 invoked by uid 500); 11 Jan 2018 19:17:10 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 13042 invoked by uid 99); 11 Jan 2018 19:17:10 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Jan 2018 19:17:10 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id E22821A095D for ; Thu, 11 Jan 2018 19:17:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.911 X-Spam-Level: X-Spam-Status: No, score=-99.911 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 5pNXwkp0Z9MA for ; Thu, 11 Jan 2018 19:17:09 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 1F6965FC0C for ; Thu, 11 Jan 2018 19:17:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7E9BFE25D6 for ; Thu, 11 Jan 2018 19:17:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id F2BD5255D9 for ; Thu, 11 Jan 2018 19:17:00 +0000 (UTC) Date: Thu, 11 Jan 2018 19:17:00 +0000 (UTC) From: "churro morales (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Reopened] (HBASE-11409) Add more flexibility for input directory structure to LoadIncrementalHFiles MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-11409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] churro morales reopened HBASE-11409: ------------------------------------ > Add more flexibility for input directory structure to LoadIncrementalHFiles > --------------------------------------------------------------------------- > > Key: HBASE-11409 > URL: https://issues.apache.org/jira/browse/HBASE-11409 > Project: HBase > Issue Type: Bug > Affects Versions: 3.0.0 > Reporter: churro morales > Assignee: churro morales > Fix For: 2.0.0-beta-2 > > Attachments: HBASE-11409.v1.patch, HBASE-11409.v2.patch, HBASE-11409.v3.patch, HBASE-11409.v4.patch, HBASE-11409.v5.patch, HBASE-11409.v6.branch-1.patch > > > Use case: > We were trying to combine two very large tables into a single table. Thus we ran jobs in one datacenter that populated certain column families and another datacenter which populated other column families. Took a snapshot and exported them to their respective datacenters. Wanted to simply take the hdfs restored snapshot and use LoadIncremental to merge the data. > It would be nice to add support where we could run LoadIncremental on a directory where the depth of store files is something other than two (current behavior). > With snapshots it would be nice if you could pass a restored hdfs snapshot's directory and have the tool run. > I am attaching a patch where I parameterize the bulkLoad timeout as well as the default store file depth. -- This message was sent by Atlassian JIRA (v6.4.14#64029)