From user-return-21694-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Tue Oct 18 21:18:46 2011 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 17F0E7FE6 for ; Tue, 18 Oct 2011 21:18:46 +0000 (UTC) Received: (qmail 78910 invoked by uid 500); 18 Oct 2011 21:18:44 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 78877 invoked by uid 500); 18 Oct 2011 21:18:44 -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 78869 invoked by uid 99); 18 Oct 2011 21:18:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2011 21:18:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of anthony.ikeda.dev@gmail.com designates 209.85.214.44 as permitted sender) Received: from [209.85.214.44] (HELO mail-bw0-f44.google.com) (209.85.214.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2011 21:18:38 +0000 Received: by bkas6 with SMTP id s6so1486488bka.31 for ; Tue, 18 Oct 2011 14:18:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=0iBlLgXb9CULhvV6DHmXy1WnWJkSHPAmiySu+xUl7fg=; b=OeeH4Hq0//zZmBFNzgpcEwKk/Ul6NjqznzQMVlrixol9x+cTZs43/dmI857rprMeJp PTeso4kwREsU7PZ67Sd014R3TiXETWHcp6ppdAUXD0buTqTIFU7u6eFI99iFJg3T1WoV 3Af9amxpKTk/oBhRBpmwy1BZqIQ7W6b/wyCoU= MIME-Version: 1.0 Received: by 10.204.41.66 with SMTP id n2mr2965055bke.77.1318972698015; Tue, 18 Oct 2011 14:18:18 -0700 (PDT) Received: by 10.204.137.138 with HTTP; Tue, 18 Oct 2011 14:18:17 -0700 (PDT) In-Reply-To: References: Date: Tue, 18 Oct 2011 14:18:17 -0700 Message-ID: Subject: Re: Using elasticsearch on cassandra nodes From: Anthony Ikeda To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec5540aa42238e204af9943d8 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec5540aa42238e204af9943d8 Content-Type: text/plain; charset=ISO-8859-1 At the moment we are only prototyping so we haven't bridged the two at all. We had planned on creating a write-through operation that allowed us to filter the calls (AOP perhaps?) to manage the indexing as we stored it in Cassandra. We are still trying to work out if we go the elastic search route or not as DataStax will be releasing DataStax Enterprise 2.0 early next year with Solr built in and as you said the index schemas seem to be difficult to deal with - I really don't want to have to configure Solr, the no schema approach sounds much faster to get up and running. Anthony On Tue, Oct 18, 2011 at 6:14 AM, Brian O'Neill wrote: > Anthony, > > We've been looking at elastic search as well. Presently we have SOLR in > place, but it is cumbersome dealing with SOLR schemas when indexing > information out of Cassandra (since you can't anticipate all the columns > ahead of time). > > What are you using as your bridge between Cassandra and ES? Are you > developing a Cassandra river? > > -brian > > > > > On Mon, Oct 17, 2011 at 5:29 PM, Anthony Ikeda < > anthony.ikeda.dev@gmail.com> wrote: > >> I've already posted to the elasticsearch groups and thought it prudent to >> also ask here. >> >> We are looking at using elastic search to index our data that we currently >> store to Cassandra. I was wondering if there are any concerns running >> elastic search on the same nodes that we use for Cassandra? We have a ring >> of 6 nodes (2 DCs each with 3 nodes) I was thinking of installing elastic >> search on 2 nodes in each datacentre - maybe all three. The only reason I'd >> use the same infrastructure would be because we have the distributed >> visibility already in place. >> >> Has anyone else taken this approach? Pros? Cons? >> >> Anthony >> >> > > > -- > Brian ONeill > Lead Architect, Health Market Science (http://healthmarketscience.com) > mobile:215.588.6024 > blog: http://weblogs.java.net/blog/boneill42/ > blog: http://brianoneill.blogspot.com/ > > --bcaec5540aa42238e204af9943d8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable At the moment we are only prototyping so we haven't bridged the two at = all. We had planned on creating a write-through operation that allowed us t= o filter the calls (AOP perhaps?) to manage the indexing as we stored it in= Cassandra.

We are still trying to work out if we go the elastic search = route or not as DataStax will be releasing DataStax Enterprise 2.0 early ne= xt year with Solr built in and as you said the index schemas seem to be dif= ficult to deal with - I really don't want to have to configure Solr, th= e no schema approach sounds much faster to get up and running.

Anthony


On= Tue, Oct 18, 2011 at 6:14 AM, Brian O'Neill <bone@alumni.brown.edu> w= rote:
Anthony,

We've been looking at e= lastic search as well.=A0 Presently we have SOLR in place, but it is cumber= some dealing with SOLR schemas when indexing information out of Cassandra (= since you can't anticipate all the columns ahead of time).=A0

What are you using as your bridge between Cassandra and ES?=A0 Are you = developing a Cassandra river?

-brian




On Mon, Oct 17, 2011 at 5:29 P= M, Anthony Ikeda <anthony.ikeda.dev@gmail.com> wro= te:
I've already posted to the elasticsearch= groups and thought it prudent to also ask here.

We are looking at using elastic search to index our data tha= t we=A0currently store to Cassandra. I was wondering if there are any=A0con= cerns running elastic search on the same nodes that we use for=A0Cassandra?= We have a ring of 6 nodes (2 DCs each with 3 nodes) I was thinking of inst= alling elastic search on 2 nodes in each datacentre - maybe all three. The = only reason I'd use the same infrastructure would be because we have th= e distributed visibility already in place.

Has anyone else taken this approach? Pros? Cons?

Anthony




--
Brian ONeill
Lead Architect, Health Market Science (= http://healthm= arketscience.com)
mobile:215.588.6024
blog: http://weblogs.java.net/blog/boneill42/
blog: http://brianoneill.blogspot.com/<= /a>


--bcaec5540aa42238e204af9943d8--