Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6625E10565 for ; Tue, 28 Apr 2015 22:58:21 +0000 (UTC) Received: (qmail 35298 invoked by uid 500); 28 Apr 2015 22:58:19 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 35224 invoked by uid 500); 28 Apr 2015 22:58:19 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 35211 invoked by uid 99); 28 Apr 2015 22:58:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Apr 2015 22:58:19 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.164.171.186 which is an MX secondary for user@hbase.apache.org) Received: from [54.164.171.186] (HELO mx1-us-east.apache.org) (54.164.171.186) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Apr 2015 22:58:12 +0000 Received: from mail-vn0-f44.google.com (mail-vn0-f44.google.com [209.85.216.44]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 1EA0040E16 for ; Tue, 28 Apr 2015 22:57:52 +0000 (UTC) Received: by vnbf1 with SMTP id f1so1425818vnb.5 for ; Tue, 28 Apr 2015 15:57:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=1PrLs6kdcD8X3O7NndDFJx1GIWq/sn4VKd498TQt5WU=; b=hALV0/oZH8TgR25bE5WezJnuAWrwV4+Xm1Qe4bKEcWSxmPP4JT55H2PxoEbafS/ABo KTKluGpd24lhiPvMfRSVpk5/NvRtMw8zmfdeg6dhHGJ66Nz9ORWFLGmkE3FjLBdAi1L2 VsjHZdutAOSYiUfBcJ/kgyTjY5yYOs0FJuBA9MCHr3jdir77mHuRtGWuALZeYtE2eahD 3dN1fmcvOM8mCZrUNoTjR8nBGwSDBwY1e/g3pMQON7ZxmKHXJ7XylNy2VbF2n55Yv3e0 B3wY9wel36f4DbIrBd9QgvVG7K2ohH2PG07v2NoskUgwiNiikFwXp7nHl7KuDTOhNMVm MVHQ== X-Gm-Message-State: ALoCoQnJab8mEUMnql6fUyiaytS78Dwkvio3DLzdbH+KGg2OO08U9q4hOPI5IFiqdRm1OPfkfwm6 X-Received: by 10.52.27.137 with SMTP id t9mr11567137vdg.86.1430261865152; Tue, 28 Apr 2015 15:57:45 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.186.4 with HTTP; Tue, 28 Apr 2015 15:57:24 -0700 (PDT) From: Jean-Marc Spaggiari Date: Tue, 28 Apr 2015 18:57:24 -0400 Message-ID: Subject: HFileOutputFormat2 with Table, which method? To: user Content-Type: multipart/alternative; boundary=20cf307d06ea6897070514d0cad8 X-Virus-Checked: Checked by ClamAV on apache.org --20cf307d06ea6897070514d0cad8 Content-Type: text/plain; charset=UTF-8 Hi all, To initialize MR jobs with HFileOutputFormat2 we need to call configureIncrementalLoad There is one with (Job, HTable) which is deprecated. There is one with (Job, Table, RegionLocator) which is not. However, I have found only HTable to implements RegionLocator. So 2nd method can not be call too. There is only configureIncrementalLoadMap(Job job, Table table) that we can call, but it's not doing all what configureIncrementalLoad is doing. So should we flag the 2 other configureIncrementalLoad methods deprecated and create a new one? Or should we make Table to implement RegionLocator? Or should HFileOutputFormat2 not be used anymore with HBase 1.0.1? Thanks, JM --20cf307d06ea6897070514d0cad8--