Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of bryanck@gmail.com designates
 209.85.210.41 as permitted sender)
Received-SPF: pass (google.com: domain of bryanck@gmail.com designates
 10.68.135.34 as permitted sender) client-ip=10.68.135.34;
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: Created date field
From: Bryan Keller <bryanck@gmail.com>
In-Reply-To: 
 <CAHau4ys-m2XzM4jP6y82Ti5G65vc0MF0EUDUNZgij2_H7jpW5A@mail.gmail.com>
Date: Fri, 24 Feb 2012 09:11:51 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <53882DD0-FDB5-48CA-9CB1-263502F4C600@gmail.com>
References: <823241BF-215E-4338-9358-E0A100703C10@gmail.com>
 <CAHau4ys-m2XzM4jP6y82Ti5G65vc0MF0EUDUNZgij2_H7jpW5A@mail.gmail.com>
To: user@hbase.apache.org

I'm thinking I could implement a coprocessor to do this. I'm still on =
0.90.4 ATM, but it's a thought going forward. I haven't played around =
with coprocessors yet though so not sure if this is feasible.

On Feb 23, 2012, at 4:05 PM, T Vinod Gupta wrote:

> do you really care about each update? you can store the created_at =
field as
> a column and use that to decide whether to put or not. the other =
option is
> to do a get with a time range less than the value you are looking for. =
if
> you get something back, then you don't need to go any further.
>=20
> thanks
>=20
> On Thu, Feb 23, 2012 at 3:57 PM, Bryan Keller <bryanck@gmail.com> =
wrote:
>=20
>> Does anyone know of any strategies for tracking the created date of a =
row
>> or column, without a checkAndPut() type of solution? I am trying to =
avoid
>> reading from the table to see if the value already exists before =
putting.
>> One thought I had was to store a timestamp of every update as a =
column, but
>> that might bloat my rows.