On Thu, Nov 17, 2011 at 10:25 AM, samal wrote:
> >> Edanuff + Beautiful People
>
> I think "row cache" could be the best fit but it can take resource
> depending on row size. It will only touch disk once (first time) in case of
> SST, rest of the req for that row will be served from memory. Try
>
>> Edanuff + Beautiful People
I think "row cache" could be the best fit but it can take resource
depending on row size. It will only touch disk once (first time) in case of
SST, rest of the req for that row will be served from memory. Try
increasing row cache size and decreasing save period to app
Thanks to samal who pointed to look at the composite columns. I am now
using composite columns names containing username+userId & valueless
column. Thus column names are now unique even for users with same name as
userId is also attached to the same composite col name. Thus the
supercolumn issue is
I think you can but I am not sure, I haven't tried that yet, Nothing harm
in keeping value also it will be read in single query only.
In 2nd case, yes 2 or more query required to get specific user details. As
username is map to user_id's key(unique like UUID) and user_id key store
actual details.
Regarding the first option that you suggested through composite columns,
can I store the username & id both in the column name and keep the column
valueless?
Will I be able to retrieve both the username and id from the composite col
name ?
Thanks a lot
On Wed, Nov 16, 2011 at 10:56 AM, Aditya Nar
Got the first option that you suggested.
However, In the second one, are you suggested to use, for e.g, key='Marcos'
& store cols, for all users of that name, containing userId inside that
row. That way it would have to read multiple rows while user is doing a
single search.
On Wed, Nov 16, 2011
> > I need to add 'search users' functionality to my application. (The
>> trigger for fetching searched items(like google instant search) is made
>> when 3 letters have been typed in).
>> >
>> > For this, I make a CF with String type keys. Each such key is made of
>> first 3 letters of a user's na
Hi Ben,
Solr, as I understood is for implementing full text
search capability within documents, but in my case, as of now I just need
to implement search on user names which seems to be easily provided
by Cassandra as user names (as column names) may be sorted alphabetically
within rows. I am spli
Hi Aditya
Not sure the best way to do in Cassandra but have you considered using
apache solr - you could then include just the row keys pointing back
to Cassandra where the actual data is.
Solr seems quite capable of performing google like searches and is fast.
Cheers
Ben
On 16/11/2011, at 1:
Any insights on this ?
On Tue, Nov 15, 2011 at 9:40 PM, Quintero wrote:
>
>
> Aditya Narayan wrote:
>
> >Hi
> >
> >I need to add 'search users' functionality to my application. (The trigger
> >for fetching searched items(like google instant search) is made when 3
> >letters have been typed in).
Aditya Narayan wrote:
>Hi
>
>I need to add 'search users' functionality to my application. (The trigger
>for fetching searched items(like google instant search) is made when 3
>letters have been typed in).
>
>For this, I make a CF with String type keys. Each such key is made of first
>3 letters
11 matches
Mail list logo
