Want to start looking into using flat storage instead (SQL won't scale). This interface contains the actions I think are needed to process an event using the current query actions.
Add a reference to the azure table storage library
Start work on a way to store query results using Azure table storage instead
Downgrade the storage client to 2.1.0.0 as the newer version doesn't seem to work too well. Initial work on a test of the performance of the flat table store to see if it's worth pursuing.
Fix so that we can actually update count fields (performance is currently bad)
Look in to batching up operations (so far I've been unable to get the kind of performance that MS says is possible, which makes this approach much slower than SQL Server)
Merge branch 'master' into flatstorage
Ugh, Couch is so close to what we want, except for the JavaScript, file size, lack of M/R chaining and other problems.

Looking in to a custom M/R system based on flat tables (WACEL already has one but it's horrible): define the interfaces that we'll need.
Add a way to chain map/reduce operations. We'll also need a way to create map/reduce operations from metrics queries.
Hm. We need to be able to 'unreduce' documents in order to be able to delete them. I'm not sure how traditional map/reduce systems handle this: it doesn't seem to be supported by the idiom: however, it's a hard requirement for our idea of user data ownership.
Add a map/reduce query representing the default 'all events' query
Change to using a key that's an array of values (this will help support CountUniqueValues which needs to be able to perform a chain operation with a new key)
Add some extra specification of how chaining will work
In order to build our queries, we'll need composable map/reduce functions, something that's not well supported by the traditional idiom. Add a 'MapResult' class to support this idea.
Initial attempt at a composable map/reduce function. We'll compose 'maps' for now, which will be sufficient for implementing AllEvents, Only and BrokenDownBy (Sum requires Reduce composition, and CountUniqueValues needs chaining)
Support 'Only' with the new query builder
Merge branch 'master' into custommapreduce

Conflicts:
	Regard.Query.Samples/Regard.Query.Samples.csproj
	Regard.Query/Regard.Query.csproj
Add implementation for BrokenDownBy
Add the logic for the 'Sum' map/reduce operation
Start work on the more complicated chained CountUniqueValues query and supporting code.