It looks like there is some interest so I'm going to disgorge everything
I've learned/considered in the past couple weeks just so that we have a
consistant base. I'm going to break down how the indexes work, different
optimizations and drawbacks and try to address the points/questions that
people h
I am not sure about the collection case. But for compact storage you can
specify multiple-ranges in a slice query.
https://issues.apache.org/jira/browse/CASSANDRA-3885
I am not sure this will get you all the way to bit-map indexes but in a
wide row scenario it seems like you could support a "even
Something like this?
SELECT * FROM users
WHERE user_id IN (select user_id from events where type in (1, 2, 3))
AND user_id NOT IN (select user_id from events where type=4)
This doesn't really look like a Cassandra query to me. More like a
query for Hive (or Drill, or Impala).
But, I know Sylv
Brian,
The Solr StatsComponent performs aggregations.
http://wiki.apache.org/solr/StatsComponent
I recommend using Datastax DSE Search...
On Fri, Apr 12, 2013 at 10:09 AM, Brian O'Neill wrote:
> @Jason,
>
> I have a lot of experience with SOLR + ES, but mainly for search. (i.e.
> Finding the
@Jason,
I have a lot of experience with SOLR + ES, but mainly for search. (i.e.
Finding the most relevant records given a query)
That's been working well, but now we have requirements to support
dashboards. Those dashboards have aggregations in them (sum, average,
count(s), etc). I have limited
