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 8CEC0184B9 for ; Thu, 26 Nov 2015 14:15:09 +0000 (UTC) Received: (qmail 45247 invoked by uid 500); 26 Nov 2015 14:15:09 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 45203 invoked by uid 500); 26 Nov 2015 14:15:09 -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 45184 invoked by uid 99); 26 Nov 2015 14:15:09 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Nov 2015 14:15:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id D9B10C12C5 for ; Thu, 26 Nov 2015 14:15:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.446 X-Spam-Level: ** X-Spam-Status: No, score=2.446 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, RP_MATCHES_RCVD=-0.554, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id bzLeEzmxm_-3 for ; Thu, 26 Nov 2015 14:15:01 +0000 (UTC) Received: from mxout26.s.uw.edu (mxout26.s.uw.edu [140.142.234.176]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 41D46428FF for ; Thu, 26 Nov 2015 14:15:01 +0000 (UTC) Received: from smtp.washington.edu (smtp.washington.edu [128.208.0.6]) by mxout26.s.uw.edu (8.14.4+UW14.03/8.14.4+UW15.02) with ESMTP id tAQEDKwN016193 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 26 Nov 2015 06:13:21 -0800 X-Auth-Received: from mail-io0-f180.google.com (mail-io0-f180.google.com [209.85.223.180]) (authenticated authid=dhutchis) by smtp.washington.edu (8.14.4+UW14.03/8.14.4+UW14.04) with ESMTP id tAQEDKg5005476 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT) for ; Thu, 26 Nov 2015 06:13:20 -0800 X-UW-Orig-Sender: dhutchis@smtp.washington.edu Received: by ioc74 with SMTP id 74so88010416ioc.2 for ; Thu, 26 Nov 2015 06:13:20 -0800 (PST) X-Received: by 10.107.6.152 with SMTP id f24mr41403928ioi.50.1448547200082; Thu, 26 Nov 2015 06:13:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.35.10 with HTTP; Thu, 26 Nov 2015 06:13:00 -0800 (PST) In-Reply-To: <5656EFEC.1090606@orkash.com> References: <5656D04A.5010002@orkash.com> <5656EFEC.1090606@orkash.com> From: Dylan Hutchison Date: Thu, 26 Nov 2015 06:13:00 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: how to maintain versioning in D4M schema? To: Accumulo User List Content-Type: multipart/alternative; boundary=001a113ee4984d2d4e0525722d44 X-PMX-Version: 6.2.1.2493963, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2015.11.26.140915 X-PMX-Server: mxout26.s.uw.edu X-Uwash-Spam: Gauge=IIIIIIII, Probability=8%, Report=' HTML_NO_HTTP 0.1, BODYTEXTH_SIZE_10000_LESS 0, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_4000_4999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, CTYPE_MULTIPART_NO_QUOTE 0, DATE_TZ_NA 0, FROM_EDU_TLD 0, NO_URI_HTTPS 0, REFERENCES 0, WEBMAIL_SOURCE 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0, __FORWARDED_MSG 0, __HAS_FROM 0, __HAS_HTML 0, __HAS_MSGID 0, __HTML_AHREF_TAG 0, __IN_REP_TO 0, __MIME_HTML 0, __MIME_VERSION 0, __PHISH_SPEAR_HTTP_RECEIVED 0, __PHISH_SPEAR_STRUCTURE_1 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS ' --001a113ee4984d2d4e0525722d44 Content-Type: text/plain; charset=UTF-8 Suppose your rowid is of the form node_timestamp Doing a prefix scan with Range.prefix("node") will cover all the nodes for any timestamp. You could choose to put the timestamp somewhere else if you need to. On Thu, Nov 26, 2015 at 3:41 AM, shweta.agrawal wrote: > 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 >> >> > > --001a113ee4984d2d4e0525722d44 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Suppose your rowid is of the form
node_timestamp
Doing a prefix scan with Range.prefix("node") w= ill cover all the nodes for any timestamp.=C2=A0 You could choose to put th= e timestamp somewhere else if you need to.


On Thu, Nov 26, 2015 at= 3:41 AM, shweta.agrawal <shweta.agrawal@orkash.com>= wrote:
=20 =20 =20
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.=C2=A0 You could append or prepend a timestamp to the rowid or column qualifier.=C2=A0 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.=C2=A0 You could also disable or relax the VersioningIterator.=C2=A0 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.=C2=A0 As in D= 4M style=C2=A0 data is only in rowid and colQualifier only.

Is there any way to achieve versioning in D4M schema?

Thanks
Shweta




--001a113ee4984d2d4e0525722d44--