hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stack <st...@duboce.net>
Subject Re: HBase design: saving two records with a same ID
Date Fri, 19 Dec 2008 21:30:13 GMT
Take a look at the lock mechanism that is available in the client API for
updates and reads.  Would that work for you?  Or look at the 'transactional'
hbase -- see
src/java/org/apache/hadoop/hbase/client/transactional/package.html.
St.Ack

On Thu, Dec 18, 2008 at 6:00 AM, Genady <genadyg@exelate.com> wrote:

> Small design question,
>
> How is possible to save a few records with the same id in Hbase? May be
> best
> way is to define for each record that has unique ID a separate table(
> tableName = recordID ) and in MapReduce for each record to check first if
> table exists, if its - add new record to existed table, otherwise create a
> new one.
>
>
>
> Genady Gilin
>
> R&D Team
>
> eXelate Media Ltd. | 20 Ha'magshimim St. Ground Floor | Petah-Tikva, Israel
>
> T: +1.646.237.4206 | M: +972.54.4824533|  <http://www.exelate.com/>
> www.exelate.com |  <mailto:genadyg@exelate.com> genadyg@exelate.com
>
>
>
> Check out our new Targeting Channels . . . Personal Tech, Urban, Fashion
> and
> more!
>
>
>
> ***This e-mail message is for the sole use of the intended recipient(s) and
> contains confidential and/or privileged information belonging to eXelate
> Media, Ltd. or its subsidiaries, customers or partners. Any unauthorized
> review, use, copying, disclosure or distribution of this message is
> strictly
> prohibited. If you are not an intended recipient of this message, please
> contact the sender by reply e-mail and destroy all soft and hard copies of
> the message and any attachments. Thank you for your cooperation.***
>
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message