Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of marcoscaixetasousa@gmail.com
 designates 209.85.223.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAEo-6+RqdPO98ZNYc_kmn-R2RriA5GSv2yTJSd-W=_RzO5OqGA@mail.gmail.com>
References: 
 <CAOTs9YHxYp4qO+U+YAuFam6BAD9+H_m2WhwmYMhoO6cB6iDgOQ@mail.gmail.com>
 <CAEo-6+RqdPO98ZNYc_kmn-R2RriA5GSv2yTJSd-W=_RzO5OqGA@mail.gmail.com>
From: Marcos Sousa <marcoscaixetasousa@gmail.com>
Date: Thu, 5 Sep 2013 11:41:20 -0300
Message-ID: 
 <CAOTs9YHGUuqCWQAxQbTw0G3m_GJvORf-YVzMb59bd_GK1z9miA@mail.gmail.com>
Subject: Re: user action modeling
To: user <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a11c3b8348b42f804e5a3ebd4

--001a11c3b8348b42f804e5a3ebd4
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Yes, that the point, I need to save dynamic parameters for each action :(

I was thinking about, distributing the data in 3 tables:
 - users: which I have all data about user and the list of friends and
documents that he performed the action
 - user_actions: to save action and futher parameters
 - objects: save the list of users who performed the action.

Replicating data like that, I will have 3 times more writing operations.

Curiously, the intersect part, aka friends who did the same action, is one
of the most used part.

Regards,

Marcos Sousa


On Thu, Sep 5, 2013 at 10:55 AM, Shahab Yunus <shahab.yunus@gmail.com>wrote:

> Your read queries seem to be more driven form the 'action' and 'object'
> perspective, rather than user.
>
> 1- So one option is that you make a composite key with action and object:
>
> action|object and the columns are users who are generating events on this
> combination. You can scan using prefix filter if you want to look at data
> specific set of action and object i.e. your requirements 1, 3 & 4. Key
> distribution should be OK too. The drawbacks here are that a) you can end
> up with really wide rows b) what if you want to store more information than
> just user id in the columns?
>
> The friends part is not that trivial and you have to maintain that
> relationship out of this main table or create complex composite entities (I
> need to think about it more, HBase is not a graph database.)
>
> Regards,
> Shahab
>
>
> On Thu, Sep 5, 2013 at 1:16 AM, Marcos Sousa
> <marcoscaixetasousa@gmail.com>wrote:
>
> > Hi,
> >
> > I'm working with HBase since the last 3 moths, now I have to store user
> > actions, at first look, using Hbase.
> >
> > I have a limited number of actions, thousands of objects and about 50
> > million users interacting with them, around 2 billion interactions per
> > month.
> >
> > I have to answer there questions:
> > How many users performed action 'foo' at object 'bar'
> > What friends performed performed action 'foo' at object 'bar'
> > What users made 'foo' at object 'bar' last week.
> > What objects received more action 'foo'
> >
> > Does anybody have suggestions to a schema for this problem?
> >
> > Best regards,
> >
> > --
> > Marcos Sousa
> >
>

--001a11c3b8348b42f804e5a3ebd4--