From user-return-37327-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Thu Oct 31 07:41:21 2013 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 52582101E1 for ; Thu, 31 Oct 2013 07:41:21 +0000 (UTC) Received: (qmail 85775 invoked by uid 500); 31 Oct 2013 07:41:18 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 85745 invoked by uid 500); 31 Oct 2013 07:41:18 -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 85737 invoked by uid 99); 31 Oct 2013 07:41:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Oct 2013 07:41:17 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [209.85.160.45] (HELO mail-pb0-f45.google.com) (209.85.160.45) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Oct 2013 07:41:11 +0000 Received: by mail-pb0-f45.google.com with SMTP id ma3so2438213pbc.18 for ; Thu, 31 Oct 2013 00:40:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:message-id:mime-version :subject:date:references:to:in-reply-to; bh=1YFE/LF0j7jCX1Ls0ZJmML6qe/Lof6DrYDmO0/ufiGw=; b=LaR2IoSZZ6XjQHY4Wu1vxPh8CigSFDGf0rHKbgO7onh2NhlA89Kt7EHFw3zYSBUeMu s4fpd2mOryulHk3Bp3QFA75O3pargl0V8fgf+GZs66DZjVJ5tZAwRo3RlehP6gybYS9O EQ+6xNoorp8l7T61hCjwlK3ej7P3y93KKWzA1D5ah1gITzJOpzX1WnifIzna3O5IjfSf 47xFP09siffQd4FnYUhGdbAHTjSxPBJUdYItZnQGM2m6X7vAnRZi3J7wTgXtwRx1nCfl kVC+1DnuoWudn+x7RON/5toLWZejpU3R7IBD8769z7OdPvuxuZpRPW+XOis8FCt6pzNS fUHA== X-Gm-Message-State: ALoCoQnS0oiw7eniz+oZyWixF6XEVZgRBDD9TvVU7AVNhn78CX1uglvDve+g6e+c7xAi3DXeybPw X-Received: by 10.68.195.36 with SMTP id ib4mr483717pbc.56.1383205249480; Thu, 31 Oct 2013 00:40:49 -0700 (PDT) Received: from [172.16.1.20] ([203.86.207.101]) by mx.google.com with ESMTPSA id y9sm3219800pas.10.2013.10.31.00.40.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 31 Oct 2013 00:40:49 -0700 (PDT) From: Aaron Morton Content-Type: multipart/alternative; boundary="Apple-Mail=_09DCEA7C-BC05-4608-8328-6957E5A29715" Message-Id: <64BEB3EA-5910-411E-BD0F-727A47028D77@thelastpickle.com> Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) Subject: Re: Searching Cassandra Date: Thu, 31 Oct 2013 20:40:42 +1300 References: To: Cassandra User In-Reply-To: X-Mailer: Apple Mail (2.1816) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_09DCEA7C-BC05-4608-8328-6957E5A29715 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 > As I understand it, where clauses only apply to primary keys and = secondary indices.=20 I=92m a little old fashioned and say if there is a query you do as part = of a hot code path it should be supported by materialising a view at = write time rather than using secondary indexes. That will give you = better performance.=20 Note that when using CQL 3 you don=92t have to specify all of the = primary key, just the partition key and then parts of the cluster key.=20= > =46rom what I've researched it appears two options are to use solr or = elasticsearch. If you want the equivalent of being able to put any term in the CQL = WHERE clause then yes those are two options.=20 Both are fine, Data Stax Enterprise includes solr and makes it a easier = http://www.datastax.com/what-we-offer/products-services/datastax-enterpris= e Or you can use the Hadoop integration if you want to process all of your = data.=20 Cheers ----------------- Aaron Morton New Zealand @aaronmorton Co-Founder & Principal Consultant Apache Cassandra Consulting http://www.thelastpickle.com On 29/10/2013, at 10:27 am, Ari King = wrote: > Hi, >=20 > I've recently started with Cassandra I'm curious about how data can be = searched. As I understand it, where clauses only apply to primary keys = and secondary indices.=20 >=20 > =46rom what I've researched it appears two options are to use solr or = elasticsearch. I'd appreciate feeback from those that have used either = of the tools as to the challenges of integrating with Cassandra. I'd = also appreciate insight on what other tools/methods are available. = Thanks. >=20 > -Ari --Apple-Mail=_09DCEA7C-BC05-4608-8328-6957E5A29715 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252
 As = I understand it, where clauses only apply to primary keys and secondary = indices. 
I=92m a little old fashioned and say if = there is a query you do as part of a hot code path it should be = supported by materialising a view at write time rather than using = secondary indexes. That will give you better = performance. 

Note that when using CQL 3 you = don=92t have to specify all of the primary key, just the partition key = and then parts of the cluster key. 

=46rom what I've researched it appears = two options are to use solr or elasticsearch.
If you = want the equivalent of being able to put any term in the CQL WHERE = clause then yes those are two options. 
Both are fine, Data Stax Enterprise includes solr = and makes it a easier http://www.datastax.com/what-we-offer/products-services/datastax-enter= prise
Or you can use = the Hadoop integration if you want to process all of your = data. 

http://www.thelastpickle.com


= --Apple-Mail=_09DCEA7C-BC05-4608-8328-6957E5A29715--