Andrew,
This is a great piece of information. Thanks.

-Jignesh

On Thu, Oct 27, 2011 at 8:05 PM, Andrew Purtell <[email protected]> wrote:

> > Any thoughts?
> > -Jignesh
>
> Read: http://ianvarley.com/UT/MR/Varley_MastersReport_Full_2009-08-07.pdf
>
>
> Best regards,
>
>
>    - Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>
>
> ----- Original Message -----
> > From: Jignesh Patel <[email protected]>
> > To: [email protected]
> > Cc:
> > Sent: Thursday, October 27, 2011 5:02 PM
> > Subject: Re: data mining
> >
> > I have tried to run a sample program only through java on the top of
> Hadoop
> > plugin for eclipse.
> > And I can see it took the time which even I can notice and I was just
> > creating a table with 3 rows.
> > My requirement is to run HBase with web application I am kind of curious
> to
> > know how stumbleupon or facebook does it.
> > I thought of using datanucleus but doesn't look like right solution.
> >
> > Any thoughts?
> >
> > -Jignesh
> >
> > On Tue, Oct 25, 2011 at 3:01 PM, Doug Meil
> > <[email protected]>wrote:
> >
> >>
> >>  And the HBase book.  (http://hbase.apache.org/book.html)
> >>
> >>  To second what JD already said, the best way to learn HBase is to use
> it.
> >>
> >>
> >>
> >>  On 10/24/11 4:32 PM, "Jean-Daniel Cryans"
> > <[email protected]> wrote:
> >>
> >>  >On Mon, Oct 24, 2011 at 1:21 PM, Jignesh Patel
> > <[email protected]>
> >>  >wrote:
> >>  >> J-D,
> >>  >>
> >>  >> Thanks for answering. Actually your suggestions gives me a good
> > starting
> >>  >> point.
> >>  >> Yes our tables are relational but not in a relational form so that
> >>  >>makes my
> >>  >> life little bit easier.  However we will have constant insertion,
> >>  >>updation
> >>  >> and few additional complexities which I do like to avoid talking.
> >>  >>
> >>  >> Another question I have here, there are four choices I can make
> > for the
> >>  >>GUI
> >>  >> based on my limited knowledge about hadoop and hbase.
> >>  >
> >>  >You should probably read up a bit more then. May I suggest:
> >>  >
> >>  >Tom White's "Hadoop: The Definitive Guide":
> >>  >http://www.amazon.com/gp/product/1449389732/
> >>  >
> >>  >And
> >>  >
> >>  >Lars George's "HBase: The Definitive Guide":
> >>  >http://www.amazon.com/dp/1449396100/
> >>  >
> >>  >>
> >>  >> 1. REST - not good for frequent transactions
> >>  >> 2. Thrift
> >>  >> 3. AVERO
> >>  >> 4. Hadoop Map-reduce
> >>  >>
> >>  >> Not sure which one to opt?
> >>  >
> >>  >The one that fits your needs.
> >>  >
> >>  >>
> >>  >> -Jignesh
> >>  >>
> >>  >>
> >>  >> On Mon, Oct 24, 2011 at 2:49 PM, Jean-Daniel Cryans
> >>  >><[email protected]>wrote:
> >>  >>
> >>  >>> That's a 250$/hr type of question, I don't think
> > you'll get much help
> >>  >>> here unless you have some more specific questions or someone
> > feels
> >>  >>> _really_ generous of their time.
> >>  >>>
> >>  >>> My free tip is going to be that you should first do a POC that
> > will
> >>  >>> lay down the basis for your project. Putting tables into the
> > HBase
> >>  >>> model can be easy and hard, it really depend on what they look
> > like.
> >>  >>> If you don't have relations and multiple keys, it's as
> > easy as putting
> >>  >>> all columns for a table into a single column family where the
> >>  >>> qualifier is the name of the SQL column. Then there's the
> > question of
> >>  >>> whether you just need to do a one-time insert or you need both
> > DBs to
> >>  >>> be in sync for some time as that's gonna require a lot
> > more brain
> >>  >>> juice!
> >>  >>>
> >>  >>> Good luck,
> >>  >>>
> >>  >>> J-D
> >>  >>>
> >>  >>> On Mon, Oct 24, 2011 at 11:17 AM, Jignesh Patel
> >>  >>><[email protected]>
> >>  >>> wrote:
> >>  >>> > We have a requirement to build Hbase based system where
> > we have to
> >>  >>> architect
> >>  >>> > to consume at least 3000-6000 tables.
> >>  >>> > Has anybody done it. I am just wondering how to architect
> > them from
> >>  >>> > relational database to nosql database.
> >>  >>> >
> >>  >>>
> >>  >>
> >>
> >>
> >
>

Reply via email to