Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-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 B38B9D218 for ; Tue, 8 Jan 2013 17:06:00 +0000 (UTC) Received: (qmail 1369 invoked by uid 500); 8 Jan 2013 17:05:58 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 1326 invoked by uid 500); 8 Jan 2013 17:05:58 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 1318 invoked by uid 99); 8 Jan 2013 17:05:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jan 2013 17:05:58 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Stephen.M.Thompson@wellsfargo.com designates 151.151.26.138 as permitted sender) Received: from [151.151.26.138] (HELO mxdcmv02i.wellsfargo.com) (151.151.26.138) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Jan 2013 17:05:51 +0000 Received: from mxicmx02.wellsfargo.com (mxicmx02.wellsfargo.com [162.102.137.63]) by mxdcmv02i.wellsfargo.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r08H5SIV004574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 8 Jan 2013 17:05:28 GMT DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=wellsfargo.com; s=2011-05-wfb; t=1357664728; bh=QeOHmXFUMCSchTYXlnHNedP2JfGPGioDezAFUVoggAU=; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; b=Nu+5JPa1Bz7zFmolVFaFDOqXeYoq9MmnAYtW6UckM09xH6kTgEGBdzEzFKulfDcOl o8QxEp+M9x1OmL76Ce95m4aN7c4Zmu5ZsOPjjL89EaqexHtOk4xK1V5gaVgLGDnUr9 aPlGFqI68q7ZzDW+kZBQmpFh8N3MmJuywxuMPPsY= Received: from msgexsil4005.ent.wfb.bank.corp (msgexsil4005.wellsfargo.com [170.13.178.15]) by mxicmx02.wellsfargo.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r08H5QlZ024411 for ; Tue, 8 Jan 2013 17:05:27 GMT Received: from MSGCMSIL1003.ent.wfb.bank.corp ([169.254.2.67]) by msgexsil4005.ent.wfb.bank.corp ([170.13.178.15]) with mapi; Tue, 8 Jan 2013 12:05:26 -0500 From: To: Date: Tue, 8 Jan 2013 12:05:26 -0500 Subject: Date Index? Thread-Topic: Date Index? Thread-Index: Ac3twbiMtMCpm7F2QuehfojjVfeW3g== Message-ID: <333B362E7B77B344A2D0FD92840282611F7F28CA3E@MSGCMSIL1003.ent.wfb.bank.corp> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_333B362E7B77B344A2D0FD92840282611F7F28CA3EMSGCMSIL1003e_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_333B362E7B77B344A2D0FD92840282611F7F28CA3EMSGCMSIL1003e_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi folks - Question about secondary indexes. How are people doing date indexes? I = have a date column in my tables in RDBMS that we use frequently, such as lo= ok at all records recorded in the last month. What is the best practice fo= r being able to do such a query? It seems like there could be an advantage= to adding a couple of columns like this: {timestamp=3D2013/01/08 12:32:01 -0500} {month=3D201301} {day=3D08} And then I could do secondary index on the month and day columns? Would th= at be the best way to do something like this? Is there any accepted "best = practice" on this yet? Thanks! Steve --_000_333B362E7B77B344A2D0FD92840282611F7F28CA3EMSGCMSIL1003e_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi folks –

<= p class=3DMsoNormal> 

Question about secondary indexes.  How are people= doing date indexes?    I have a date column in my tables in= RDBMS that we use frequently, such as look at all records recorded in the = last month.  What is the best practice for being able to do such a que= ry?  It seems like there could be an advantage to adding a couple of c= olumns like this:

 

  &n= bsp;            = ; {timestamp=3D2013/01/08 12:32:01 -0500}

  &nb= sp;            = {month=3D201301}

      &nb= sp;         {day=3D08}

 

And then I could do secondary index on the m= onth and day columns?  Would that be the best way to do something like= this?  Is there any accepted “best practice” on this yet?=

 

Thanks!

Steve=

= --_000_333B362E7B77B344A2D0FD92840282611F7F28CA3EMSGCMSIL1003e_--