It seems like you don't really need a search, but just filtering, so, you'd use a subset of features from ElasticSearch. But why would you think you cannot use ES as DB? What would be your concern? Just, so you know, I use ES as the only storage for one of my project for second year already, for Big Data/BigTraffic application. And if you do things right, you should be allright as well.
Eugene On Monday, January 13, 2014 5:31:24 AM UTC-5, Xie Lebing wrote: > > Not a joke. > > We have events log (userid, timestamp, action, entity ....) which records > players' essential activities and is used for customer service. The volume > is around 10-15 million rows a day and held for 3 months. The search > condition could be complicated, such like userid + time range + activities; > timerange + activities so on. > > Currently 3 solutions are considered: > > 1. Use MongoDB cluster to hold the data. > 2. Use ES to index the log and for searching. Easy to setup and maintain. > 3. Use HBASE, but have to create multiple "indexes" > > any idea about that? Thanks! > > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/98c63853-9faf-4d0c-912a-1698fbf91399%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
