Thank you very much the suggestion. Looks like this is the option I want to
go for.


-Jignesh


On Wed, Feb 19, 2014 at 1:03 AM, James Taylor <[email protected]>wrote:

> Hi Jignesh,
> Phoenix has support for multi-tenant tables:
> http://phoenix.incubator.apache.org/multi-tenancy.html. Also, your primary
> key constraint would transfer over as-is, since Phoenix supports composite
> row keys. Essentially your pk constraint values get concatenated together
> to form your row key in HBase. We do not support unique constraints yet,
> but we do support secondary indexing:
> http://phoenix.incubator.apache.org/secondary_indexing.html
>
> HTH. Thanks,
>
> James
>
>
> On Tue, Feb 18, 2014 at 6:06 PM, Jean-Marc Spaggiari <
> [email protected]> wrote:
>
> > You might want to take a look at Phoenix
> > http://phoenix.incubator.apache.org/
> >
> > JM
> >
> >
> > 2014-02-18 19:29 GMT-05:00 Jignesh Patel <[email protected]>:
> >
> > > Jean,
> > >
> > > We have a product which is working on mysql and we are trying to move
> it
> > on
> > > HBase to create multi-tenant database.
> > > I agree with you that because of nosql nature of database, we should
> > > denormalize the mysql database. However, was thinking of making quick
> > > progress by first creating dirty structure of existing database in
> > > hbase(from mysql) and than optimizing/modifying in nosql way.
> > >
> > >
> > >
> > > On Tue, Feb 18, 2014 at 4:11 PM, Jean-Marc Spaggiari <
> > > [email protected]> wrote:
> > >
> > > > Moving the discussion to the user mailing list.
> > > >
> > > > Hi Jignesh,
> > > >
> > > > You can not really map mysql tables to HBase. You need to rethink
> your
> > > > schema when moving to HBase. Like in MySQL, a key can be on multiple
> > > > columns. In HBase, it's they key itself. etc.
> > > >
> > > > What are you trying to achieve?
> > > >
> > > > JM
> > > >
> > > >
> > > > 2014-02-18 15:19 GMT-05:00 Jignesh Patel <[email protected]>:
> > > >
> > > > > Has anybody used for creating tables from msyql to Hbase through
> > cloud
> > > > > graph?
> > > > >
> > > >
> > >
> >
>

Reply via email to