This is basically what I do only I use a Java Client to aggregate and place the
data into HBase. I can process a log with a million rows in a little over 13
seconds. To write the data to HBase takes around 40 seconds. Then we hit HBase
via a thin client a SpringWS. Seems to work pretty well.
-P
I had a problem of lost rows when the flush was right before the close
statement.
Sean Sechrist wrote:
=
Accidentally dropped the user list of this email exchange. Anyone have any
other ideas here?
But using scanner caching of 1 fixes the problem, as suspected. So now I'll
inv
Sounds like we are doing the same thing. I am hitting an HBase backend from an
Ajax frontend (via Spring MVC) to access our log files to generate the same
type of reports. Most of the time I get sub-second response. Longest is around
8 seconds. This was my first try at HBase and my next rev. wil
