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 8CC0D18AD0 for ; Thu, 26 Nov 2015 16:52:33 +0000 (UTC) Received: (qmail 92400 invoked by uid 500); 26 Nov 2015 16:52:28 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 92344 invoked by uid 500); 26 Nov 2015 16:52:28 -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 92334 invoked by uid 99); 26 Nov 2015 16:52:28 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Nov 2015 16:52:28 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id C615D1A0A7E for ; Thu, 26 Nov 2015 16:52:27 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.88 X-Spam-Level: ** X-Spam-Status: No, score=2.88 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 2q7yPSaVXYCH for ; Thu, 26 Nov 2015 16:52:22 +0000 (UTC) Received: from mail-vk0-f51.google.com (mail-vk0-f51.google.com [209.85.213.51]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id B7D35428E7 for ; Thu, 26 Nov 2015 16:52:21 +0000 (UTC) Received: by vkbs1 with SMTP id s1so56270021vkb.1 for ; Thu, 26 Nov 2015 08:52:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=i326MDFDHKtUjSt7BLvdjOO7THQShB1MS/uaqnYWSSM=; b=dE016jn+C75Wv42jw2GLE/tAfSLn4y1InwrkXA4XUScULeWnB8g59Sul36t2Cx2+hb fDwEg/wrBF/Bah0Q3JHMB1rQpfPOOqlE4/d0NxbD9LgII4vO6Cuv8j7P5pDFnIjbr35c A3q0lvGwBCq7A+yzApNVaDXqmRLRGEmB09d8qTMPcCUNNg/pPktzQksvlYbBl8EZ5cXy J0K/sgj1DgjrnPIS/1mMPC7srpNj+oP0jWYc2gVHGYvIgO+UbBdKmxyR1LJCkyATshOH ONvMoDE2KBy35crbT4SdKQo0mnpWEMHqx1J8AjRpnEuY0/TO2X2LfATF4dDS7VaNboWx v2lQ== MIME-Version: 1.0 X-Received: by 10.31.52.211 with SMTP id b202mr38588929vka.82.1448556741414; Thu, 26 Nov 2015 08:52:21 -0800 (PST) Received: by 10.31.171.85 with HTTP; Thu, 26 Nov 2015 08:52:21 -0800 (PST) In-Reply-To: <5656D04A.5010002@orkash.com> References: <5656D04A.5010002@orkash.com> Date: Thu, 26 Nov 2015 11:52:21 -0500 Message-ID: Subject: Re: how to maintain versioning in D4M schema? From: David Medinets To: accumulo-user Content-Type: multipart/alternative; boundary=001a1143e98802594c05257466bb --001a1143e98802594c05257466bb Content-Type: text/plain; charset=UTF-8 What are the query patterns? If you are versioning for auditing then changing the VersioningIterator seems the easiest approach. You could also store application-specific version information in the column family. One of the reasons that D4M does not use it is to allow application-specific uses. Using the CF means that any applications that understand D4M would not need to change their queries to adjust for the version information. On Thu, Nov 26, 2015 at 4: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 > > --001a1143e98802594c05257466bb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
What are the query patterns? If you are versioning for aud= iting then changing the VersioningIterator seems the easiest approach. You = could also store application-specific version information in the column fam= ily. One of the reasons that D4M does not use it is to allow application-sp= ecific uses. Using the CF means that any applications that understand D4M w= ould not need to change their queries to adjust for the version information= .

On Thu= , Nov 26, 2015 at 4:26 AM, shweta.agrawal <shweta.agrawal@orkash.c= om> wrote:
Hi,

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

Is there any way to achieve versioning in D4M schema?

Thanks
Shweta


--001a1143e98802594c05257466bb--