Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of anthony.ikeda.dev@gmail.com
 designates 209.85.210.172 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1244.3)
Subject: Re: Best indexing solution for Cassandra
From: Ikeda Anthony <anthony.ikeda.dev@gmail.com>
In-Reply-To: 
 <CAOT3TWpORPtUGNHK87jv3SWkvcHqQb8qVhJDex_FCnx2QfNfkA@mail.gmail.com>
Date: Thu, 29 Sep 2011 09:30:18 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <87466F03-AA07-4A1D-97B1-6DEF1862EED0@gmail.com>
References: 
 <CAFk=5qAceoi4nH3rLuyZU_PqxLDm+M+zx0eqa_-4fk=FmzMj1g@mail.gmail.com>
 <1317242745.69767.YahooMailNeo@web130113.mail.mud.yahoo.com>
 <CAOT3TWpORPtUGNHK87jv3SWkvcHqQb8qVhJDex_FCnx2QfNfkA@mail.gmail.com>
To: user@cassandra.apache.org

=46rom a usability standpoint, elastic search is looking promising. I'll =
have to get more info through use on it's distribution as well.

Thanks

:)


On 28/09/2011, at 14:01 PM, Mohit Anchlia wrote:

> look at elasticsearch too. It shards differently.
>=20
> On Wed, Sep 28, 2011 at 1:45 PM, Rafael Almeida <almeidaraf@yahoo.com> =
wrote:
>> =46rom Anthony Ikeda <anthony.ikeda.dev@gmail.com>:
>>> Well, we go live with our project very soon and we are now looking =
into what we will be doing for the next phase. One of the enhancements =
we would like to consider is an indexing platform to start building =
searches into our application.
>>>=20
>>>=20
>>> Right now we are just using column families to index the information =
(different views based on what we want to find) however it is proving to =
be quite a task to keep the index views in sync with the data - although =
not a showstopper, it isn't something we want to be handling all the =
time especially since operations like deletions require changes to =
multiple column families.
>>>=20
>>>=20
>>> I've heard of Solandra and Lucandra but I want to understand the =
experiences of people that may have used them or other suggestions.
>>=20
>>=20
>> I've had some experience with that. My main problem was that I had a =
limited vocabulary and a large number of documents. It seems like =
solandra kept all my documents on the same row for a given term. That =
means the documents don't get spread out throught the cluster and search =
was painfully slow. We ended up rolling up our own solution and not =
using cassandra at all for that purpose (althought we still use it for =
storage).
>>=20
>>=20