Thank you very much. This was very helpfull. I'll post an update here when I
managed to finish my datastructure design.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Datastructure-time-tracking-tp7005672p7011370.html
Sent from the cassandra-u...
On Fri, Nov 18, 2011 at 1:59 PM, RobinUs2 wrote:
> We should be able to:
> - find all time records from all users within a given project (with
> optionally a certain date range)
>
You'll need a timeline per project. I would use one row per day, week, or
month, depending on the size. Your row k
We should be able to:
- find all time records from all users within a given project (with
optionally a certain date range)
- find total time per task
- find all time records from user X (with optionally a certain date range)
As I understand from your answer this would require atleast 3 (or 5?) CF'
On Thu, Nov 17, 2011 at 2:36 PM, RobinUs2 wrote:
> We're currently developing a system with a time tracking part. We need to
> store following details:
> - user
> - time (in minutes)
> - description
> - billable
> - project
> - task ID
>
> What would be a proper data structure for this in Cassand
