I will frame my question in a different way.
Each user in my system subscribes to updates from selected other users
(updates are aggregated from outside) and tags the users to which he/she
is subscribed to.
In my current design, I have a column family called "Followers" keyed by
userid in w
One approach is to ask yourself questions as to how you would use this
information, for example
- how often to you go from user to tags
- how often would you want to go from tag->users.
- What kind of reporting would you want to do on tags and how often
- Can multiple people add the sa
I have a very similar use case in my system, I've solved it as follows;
If all your users have a unique id, such as a login userid.
You could create a new column family, keyed by the userid, and add columns
which have no value, but the column name is the tag value.
Searching these tags later will
