Would hbase + elasticsearch be faster than just elasticsearch in this case?

I am building a stat aggregator, where the rows are a long string of
boolean values. I will be doing two types of queries, sequential
searches for data points for a graph, and aggregation given a range of
dates. Given that hbase stores things sequentially, would I have
faster read times by using hbase + elasticsearch, rather than
elasticsearch alone as my only data store?

hbase is really fast for sequential access, as for fast or not, it mostly
depends if all your different type of aggregation can work in sequential
access (and you need to implement the aggregation, assuming you compare it
to facets in elasticsearch).

On Mon, Aug 8, 2011 at 4:50 PM, Jeremy Smith xperts@gmail.com wrote:

I am building a stat aggregator, where the rows are a long string of
boolean values. I will be doing two types of queries, sequential
searches for data points for a graph, and aggregation given a range of
dates. Given that hbase stores things sequentially, would I have
faster read times by using hbase + elasticsearch, rather than
elasticsearch alone as my only data store?