Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 michael_segel@hotmail.com does not designate 54.164.171.186 as permitted
 sender)
Message-ID: <BLU436-SMTP23908E7207109E7314F13D68FD60@phx.gbl>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Subject: Re: Hbase row ingestion ..
From: Michael Segel <michael_segel@hotmail.com>
In-Reply-To: <554289C7.6060103@upsight.com>
Date: Thu, 30 Apr 2015 16:20:58 -0500
Content-Transfer-Encoding: quoted-printable
References: 
 <CAMP4i_PsfB3_-uSh46qdB6RiUcp_7L2D8Opuy1sd87+_WCSZcw@mail.gmail.com>
 <CAMP4i_OwULvsSux--QtrB2-XfMREm0o2GVQTNXjkSJmkVmSMBg@mail.gmail.com>
 <CALPvCiAOxqsUhaacngcKOO-0H-9Jpy1YoN6dsEtCrJun3nzqaQ@mail.gmail.com>
 <CAMP4i_MddPh97Mq3kMQXAHr5RBmFOVwo5vHKtc986icfFYH7eQ@mail.gmail.com>
 <BLU436-SMTP91C50F3DBFD2318F723FF98FD60@phx.gbl>
 <AA3F2BD7-969D-4670-ABF5-F89F3FFAC921@gmail.com>
 <CAMP4i_Nd89fGZB-3Ysni5NLyyHW1B0+Sir5Uap_90B2hbcDQMg@mail.gmail.com>
 <BLU436-SMTP115CA22C3B5ED8EFD2FE3168FD60@phx.gbl>
 <554289C7.6060103@upsight.com>
To: user@hbase.apache.org

Exactly!

So if you don=E2=80=99t need to know if your table is bucketed or not.=20=

You just put()  or get()/scan() like it any other table.=20

> On Apr 30, 2015, at 3:00 PM, Andrew Mains <andrew.mains@kontagent.com> =
wrote:
>=20
> Thanks all again for the replies--this is a very interesting =
discussion :).
>=20
> @Michael HBASE-12853 is definitely an interesting proposition for our =
(Upsight's) use case--we've done a moderate amount of work to make our =
reads over the bucketed table efficient using hive. In particular, we =
added support for predicate pushdown to multiple scans, which allows us =
to read only a specific range within each bucket--see HIVE-7805. If I =
understand correctly, with HBASE-12853 we could make that pushdown work =
transparently--that is, the client code could just push down a single =
scan, which would then be fanned out to each bucket. It would certainly =
make our code somewhat cleaner (we currently create a scan with our =
predicate for each bucket, and then push all of those to =
MultiTableInputFormat).
>=20
> Best,
>=20
> Andrew
>=20
>=20
> On 4/30/15 12:36 PM, Michael Segel wrote:
>> The downside
>> >>here is that you will lose your ability to perform range scans
>=20
>=20

The opinions expressed here are mine, while they may reflect a cognitive =
thought, that is purely accidental.=20
Use at your own risk.=20
Michael Segel
michael_segel (AT) hotmail.com