3 ms·

Thanks, that's very much what I'm talking about. Cassandra would be my ideal store, I absolutely love it except for the ability to index across nodes. My unde

Thanks, that's very much what I'm talking about. Cassandra would be my ideal store, I absolutely love it except for the ability to index across nodes. My understanding, when last I looked at it, was that indexes were only local and didn't span Cassandra nodes. Does Cassandra now have properly distributed indexes? When I was looking at implementing Cassandra instead of Mongo DB, it seemed like we had to create reverse column family (IIRC, been away from Cassandra for a bit now). Is that still the case?

crypto5 13y ago
Just curious: did you get any real problem with local indexes? For me it works just fine.
- craigching 13y ago
  How do you use a local index when your data is distributed across numerous nodes? Maybe I'm missing something fundamental, so I'd definitely like to understand.
  - crypto5 13y ago
    It's hidden from me behind client library API(astyanax in my case), I shouldn't know anything about index locality. I just send request(give me records for this index value), and get response and don't care if it's local index or distributed index. Astyanax takes care about everything, it queries all nodes.
    - craigching 13y ago
      I will check that out, thanks! I was looking at Hector and Pelops at the time and I don't believe they provided anything like that. But now that you mention it, I bet Hive could do what you describe as well. Need to dig a bit deeper now!
    - craigching 13y ago
      Just refreshing my memory here, but this blog post [1] is what kept me away from secondary indexes and explains why I need something more from Cassandra. Especially the section on "The Good: Secondary Indexes", I actually have some data that is stored by timestamp, that was, as I recall, the biggest turn-off on them. Has the state of affairs advanced since a year ago? Would love to hear it has! [1] http://brianoneill.blogspot.com/2012/03/cassandra-indexing-good-bad-and-ugly.html http://brianoneill.blogspot.com/2012/03/cassandra-indexing-g...

crypto5 13y ago

Just curious: did you get any real problem with local indexes? For me it works just fine.

craigching 13y ago
How do you use a local index when your data is distributed across numerous nodes? Maybe I'm missing something fundamental, so I'd definitely like to understand.
- crypto5 13y ago
  It's hidden from me behind client library API(astyanax in my case), I shouldn't know anything about index locality. I just send request(give me records for this index value), and get response and don't care if it's local index or distributed index. Astyanax takes care about everything, it queries all nodes.
  - craigching 13y ago
    I will check that out, thanks! I was looking at Hector and Pelops at the time and I don't believe they provided anything like that. But now that you mention it, I bet Hive could do what you describe as well. Need to dig a bit deeper now!
  - craigching 13y ago
    Just refreshing my memory here, but this blog post [1] is what kept me away from secondary indexes and explains why I need something more from Cassandra. Especially the section on "The Good: Secondary Indexes", I actually have some data that is stored by timestamp, that was, as I recall, the biggest turn-off on them. Has the state of affairs advanced since a year ago? Would love to hear it has! [1] http://brianoneill.blogspot.com/2012/03/cassandra-indexing-good-bad-and-ugly.html http://brianoneill.blogspot.com/2012/03/cassandra-indexing-g...