I'm new to ES and i'm trying to figure out if a certain scenario is possible before making a decision on using ES. Here is the scenario: I have millions of events that are tied to employees, each event also contains the employee id so no need for a join, data duplication and flat tables are fine. I'll like to store these events in ES in such a way that I can run queries across multiple events and employees in sequence that match a specific pattern.
Ok, there is an example, I'll like to be able to run a query that returns all employees that did X and then did y and then did z in that order between 1/2/1024 and 1/31/2014 and it will return a distinct list/group of employees or employee id's. The key point is the *then*, its ok if the employee did other things in between, it would be nice to enforce that but for now I just need the basic working. in non search world, the solution will most likely be iterating over a subset of queries. Meaning give me all users that did X and store somewhere and then another query to give me a subset of the result from query 1 that did Y, etc...but I figured there has to be a better way. Any ideas or suggestions will be greatly appreciated. -- 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/1fde2820-6f99-45c8-9003-7b1d10139ca9%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
