Return-Path: X-Original-To: apmail-accumulo-user-archive@www.apache.org Delivered-To: apmail-accumulo-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 1B43918E3D for ; Thu, 26 Nov 2015 11:41:49 +0000 (UTC) Received: (qmail 39313 invoked by uid 500); 26 Nov 2015 11:41:48 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 39259 invoked by uid 500); 26 Nov 2015 11:41:48 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 39249 invoked by uid 99); 26 Nov 2015 11:41:48 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Nov 2015 11:41:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 6AE83180A81 for ; Thu, 26 Nov 2015 11:41:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id aGWqwTNYe7q0 for ; Thu, 26 Nov 2015 11:41:41 +0000 (UTC) Received: from smtp113.ord1c.emailsrvr.com (smtp113.ord1c.emailsrvr.com [108.166.43.113]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 4A47D42B08 for ; Thu, 26 Nov 2015 11:41:41 +0000 (UTC) Received: from smtp23.relay.ord1c.emailsrvr.com (localhost.localdomain [127.0.0.1]) by smtp23.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 2E5CF280288; Thu, 26 Nov 2015 06:41:35 -0500 (EST) X-Auth-ID: shweta.agrawal@orkash.com Received: by smtp23.relay.ord1c.emailsrvr.com (Authenticated sender: shweta.agrawal-AT-orkash.com) with ESMTPSA id 84C7B280252 for ; Thu, 26 Nov 2015 06:41:34 -0500 (EST) X-Sender-Id: shweta.agrawal@orkash.com Received: from [192.168.0.119] ([UNAVAILABLE]. [14.141.49.198]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA) by 0.0.0.0:465 (trex/5.5.4); Thu, 26 Nov 2015 06:41:35 -0500 Message-ID: <5656EFEC.1090606@orkash.com> Date: Thu, 26 Nov 2015 17:11:32 +0530 From: "shweta.agrawal" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 MIME-Version: 1.0 To: user@accumulo.apache.org Subject: Re: how to maintain versioning in D4M schema? References: <5656D04A.5010002@orkash.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------000403080208040100080303" This is a multi-part message in MIME format. --------------000403080208040100080303 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit If I append timestamp on rowid. The id which acts as a node will act as a different entity. How this will be maintained? Thanks Shweta On Thursday 26 November 2015 04:50 PM, Dylan Hutchison wrote: > Hi Shweta, > > You have lots of options. You could append or prepend a timestamp to > the rowid or column qualifier. When prepending to the rowid, you may > want to reverse the timestamp in order to better shard your data (that > is, prevent all updates at a particular time from going to a single > tablet server), at the expense of not being able to do range queries > on time periods. You could also disable or relax the > VersioningIterator. It depends on what you want to do. > > On Thu, Nov 26, 2015 at 1:26 AM, shweta.agrawal > > wrote: > > Hi, > > I have my data stored in D4M style. I also want to maintain > versions of different value on the basis of time. As in D4M > style data is only in rowid and colQualifier only. > > Is there any way to achieve versioning in D4M schema? > > Thanks > Shweta > > --------------000403080208040100080303 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
If I append timestamp on rowid. The id which acts as a node will act as a different entity.
How this will be maintained?

Thanks
Shweta

On Thursday 26 November 2015 04:50 PM, Dylan Hutchison wrote:
Hi Shweta,

You have lots of options.  You could append or prepend a timestamp to the rowid or column qualifier.  When prepending to the rowid, you may want to reverse the timestamp in order to better shard your data (that is, prevent all updates at a particular time from going to a single tablet server), at the expense of not being able to do range queries on time periods.  You could also disable or relax the VersioningIterator.  It depends on what you want to do.

On Thu, Nov 26, 2015 at 1:26 AM, shweta.agrawal <shweta.agrawal@orkash.com> wrote:
Hi,

I have my data stored in D4M style. I also want to maintain versions of different value on the basis of time.  As in D4M style  data is only in rowid and colQualifier only.

Is there any way to achieve versioning in D4M schema?

Thanks
Shweta



--------------000403080208040100080303--