phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randy Hu <>
Subject Re: Best strategy for UPSERT SELECT in large table
Date Sat, 17 Jun 2017 23:06:21 GMT
If I count the number of tailing zeros correctly, it's 15 billion records,
any solution based on HBase PUT interaction (UPSERT SELECT) would probably
take way more time than your expectation. It would be better to use the
map/reduce based bulk importer provided by Phoenix:

The importer leverages HBase bulk mode to convert all data into HBase
storage file, then hand it over to HBase in the final stage, thus avoids
all network and disk random access cost when going through HBase region


On Fri, Jun 16, 2017 at 9:51 AM, Pedro Boado [via Apache Phoenix User List]
<> wrote:

> Hi guys,
> We are trying to populate a Phoenix table based on a 1:1 projection of
> another table with around records via an UPSERT SELECT in
> phoenix client. We've noticed a very poor performance ( I suspect the
> client is using a single-threaded approach ) and lots of issues with client
> timeouts.
> Is there a better way of approaching this problem?
> Cheers!
> Pedro
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> Best-strategy-for-UPSERT-SELECT-in-large-table-tp3675.html
> To start a new topic under Apache Phoenix User List, email
> To unsubscribe from Apache Phoenix User List, click here
> <>
> .
> <>

View this message in context:
Sent from the Apache Phoenix User List mailing list archive at

View raw message