:10,0' : {meta}
> …
> '1:20, 10': {meta}
> }
On Jun 29, 2012, at 5:13 PM, Peter Hsu wrote:
> I have a question on what the best way is to store the data in my schema.
>
> The data
> I have millions of nodes, each with a different cartesian coordinate. The
I have a question on what the best way is to store the data in my schema.
The data
I have millions of nodes, each with a different cartesian coordinate. The keys
for the nodes are hashed based on the coordinate.
My search is a proximity search. I'd like to find all the nodes within a given
di
I have a pretty simple data modeling question. I don't know whether or not to
use a CF or SCF in one instance.
Here's my example. I have an Store entry and locations for each store. So I
have something like:
Using CF:
Store { //CF
storeId { //row key
storeName:str,
storeLogo:i
Correct me if I'm wrong here. Even though you can get your results with Random
Partitioner, it's a lot less efficient if you're going across different
machines to get your results. If you're doing a lot of range queries, it makes
sense to have things ordered sequentially so that if you do need
Hi All,
This may have been answered already, but I did a [quick] Google search and
didn't find much. Which is the better Java client to use? Hector or
cassandra-java-client or neither?
it seems Hector is more fully featured and more active as a project in general.
What are user experiences w
ra and its siblings are weak at ad hoc queries on tables
> that you did not think to index in advance
>
> On Mon, May 10, 2010 at 11:06 AM, Peter Hsu wrote:
>> I've seen a lot of threads and posts about why Cassandra is great. I'm
>> fairly sold on the featu
I've seen a lot of threads and posts about why Cassandra is great. I'm fairly
sold on the features, and the few big deployments on Cassandra give it a lot of
credibility.
However, I don't believe in magic bullets, so I really want to understand the
potential downsides of Cassandra. Right now,
