to
use cassandra to solve the following cases:
Ability to fetch entries by applying a few filters ( like show me only likes
from a given user). This would include range query to support pagination. So
this would mean indices on a few columns like the feed id, feed type etc.
Sounds like you've
entries by applying a few filters ( like show me only
likes from a given user). This would include range query to support
pagination. So this would mean indices on a few columns like the feed id,
feed type etc.
2. We have around 3 machines with 4GB RAM for this purpose and thinking
On Wed, 2010-04-14 at 06:45 -0300, Jesus Ibanez wrote:
Option 1 - insert data in all different ways I need in order to be
able to query?
Rolling your own indexes is fairly common with Cassandra.
Option 2 - implement Lucandra? Can you link me to a blog or an article
that guides me on how
in the future, if my website grows.
Thenks for your answer Eric!
Jesús.
2010/4/14 Eric Evans eev...@rackspace.com
On Wed, 2010-04-14 at 06:45 -0300, Jesus Ibanez wrote:
Option 1 - insert data in all different ways I need in order to be
able to query?
Rolling your own indexes is fairly common
this message in context:
http://n2.nabble.com/Lucandra-or-some-way-to-query-tp4900727p4905149.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
.nabble.com/Lucandra-or-some-way-to-query-tp4900727p4905149.html
Sent from the cassandra-u...@incubator.apache.org mailing list archive at
Nabble.com.
Hi
I've been thinking of using cassandra for our existing application, which
has a very complex RDBMS schema as of now, and we need to make a lot of
queries using joins and where.
Whereas we can eliminate joins by using duplicate entries, its still hard to
query cassandra. I have thought of a way
On 11 April 2010 07:59, Lucifer Dignified vineetdan...@gmail.com wrote:
For a very simple query wherin we need to check username and password I
think keeping incremental numeric id as key and keeping the name and value
same in the column family should work.
It is highly unlikely that your
simple query wherin we need to check username and password I
think keeping incremental numeric id as key and keeping the name and value
same in the column family should work.
It is highly unlikely that your application has enough usernames/passwords
that you need Cassandra to store them
Hi All：
I am thinking a more precise query in Cassandra:
Could we hava a query API like this :
ListColumnOrSuperColumn get_slice_condition(String keyspace, ListString
keys, ColumnParent column_parent, MapColumnName, QueryCondition
queryConditions, int consistency_level)
So we could use
On Wed, Mar 24, 2010 at 4:57 AM, Colin Vipurs zodiac...@gmail.com wrote:
...
ColumnFamily {
'key1' {
'SuperColumn1' {
'Column1' : somevalue
'Column2' : somevalue
}
'SuperColumn2' {
'Column3' : somevalue
}
}
'key2' {
'SuperColumn1'
I'm not doing schema migration, but I suspect my lack of experience
and understanding of column-based data is clouding the issue. What I
have is 2 pieces of information, let's call them LH and RH and a
single long value representing the link between them, S. The data
needs to be ordered by S, so
1101 - 1112 of 1112 matches
Mail list logo
