Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of dontariq@gmail.com designates
 209.85.220.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <BLU0-SMTP216C10683D4CA80FC39BBE58F290@phx.gbl>
References: <1357380684848-4036184.post@n3.nabble.com>
 <CADK=YxvUiBaGZzjhX8yV3P+xfcJZAn8wF7=_J1zqtguFRDDjHw@mail.gmail.com>
 <CADSMiU_QPEyY9W7e7Qa+qOCza3XMSQxepMh9TDEA8AgFPVPq+g@mail.gmail.com>
 <CA+RK=_Bto1neL3nS89k5Ecz58kaQC7sqmr5po0CZeMChwp0xrw@mail.gmail.com>
 <3702994083872207037@unknownmsgid>
 <CA+RK=_BDWMQYLhZSOGhsKmbydz=Xk5j+2uY0HSv0ED37bUtcjA@mail.gmail.com>
 <CA+RK=_DUqn41hCnbkZqRpxJ6Wwtnxoxx4Jy3Oas_cFG_oJxFpA@mail.gmail.com>
 <CAOT3TWqT4QL+kveZHT70g-78EAQvWT+-y_c==+XmDsPg4Ky7oQ@mail.gmail.com>
 <CAHyy+G-mcPDavxn3MgL2dEjJKLPBY171Y6Jz-mqsnr1opJWtEg@mail.gmail.com>
 <1357876263.21531.YahooMailNeo@web140603.mail.bf1.yahoo.com>
 <CAAXmExWrU+WZsiq7U=mzAcBzBwEh0HSw-apboHV_N1fbVqPfYg@mail.gmail.com>
 <BLU0-SMTP216C10683D4CA80FC39BBE58F290@phx.gbl>
From: Mohammad Tariq <dontariq@gmail.com>
Date: Fri, 11 Jan 2013 20:57:47 +0530
Message-ID: 
 <CAMVC6ROcdTkS2CTT8DZ4XNAhgiE22KMr=ErMLzH5XrjUKUt5vA@mail.gmail.com>
Subject: Re: Storing images in Hbase
To: "user@hbase.apache.org" <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=14dae9cdc0f373a20104d304f222

--14dae9cdc0f373a20104d304f222
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

IMHO, if the image files are not too huge, Hbase can efficiently serve the
purpose. You can store some additional info along with the file depending
upon your search criteria to make the search faster. Say if you want to
fetch images by the type, you can store images in one column and its
extension in another column(jpg, tiff etc).

BTW, what exactly is the problem which you are facing. You have written
"But I still cant do it"?

Warm Regards,
Tariq
https://mtariq.jux.com/


On Fri, Jan 11, 2013 at 8:30 PM, Michael Segel <michael_segel@hotmail.com>w=
rote:

> That's a viable option.
> HDFS reads are faster than HBase, but it would require first hitting the
> index in HBase which points to the file and then fetching the file.
> It could be faster... we found storing binary data in a sequence file and
> indexed on HBase to be faster than HBase, however, YMMV and HBase has bee=
n
> improved since we did that project....
>
>
> On Jan 10, 2013, at 10:56 PM, shashwat shriparv <dwivedishashwat@gmail.co=
m>
> wrote:
>
> > Hi Kavish,
> >
> > i have a better idea for you copy your image files to a single file on
> > hdfs, and if new image comes append it to the existing image, and keep
> and
> > update the metadata and the offset to the HBase. Because if you put
> bigger
> > image in hbase it wil lead to some issue.
> >
> >
> >
> > =E2=88=9E
> > Shashwat Shriparv
> >
> >
> >
> > On Fri, Jan 11, 2013 at 9:21 AM, lars hofhansl <larsh@apache.org> wrote=
:
> >
> >> Interesting. That's close to a PB if my math is correct.
> >> Is there a write up about this somewhere? Something that we could link
> >> from the HBase homepage?
> >>
> >> -- Lars
> >>
> >>
> >> ----- Original Message -----
> >> From: Jack Levin <magnito@gmail.com>
> >> To: user@hbase.apache.org
> >> Cc: Andrew Purtell <apurtell@apache.org>
> >> Sent: Thursday, January 10, 2013 9:24 AM
> >> Subject: Re: Storing images in Hbase
> >>
> >> We stored about 1 billion images into hbase with file size up to 10MB.
> >> Its been running for close to 2 years without issues and serves
> >> delivery of images for Yfrog and ImageShack.  If you have any
> >> questions about the setup, I would be glad to answer them.
> >>
> >> -Jack
> >>
> >> On Sun, Jan 6, 2013 at 1:09 PM, Mohit Anchlia <mohitanchlia@gmail.com>
> >> wrote:
> >>> I have done extensive testing and have found that blobs don't belong =
in
> >> the
> >>> databases but are rather best left out on the file system. Andrew
> >> outlined
> >>> issues that you'll face and not to mention IO issues when compaction
> >> occurs
> >>> over large files.
> >>>
> >>> On Sun, Jan 6, 2013 at 12:52 PM, Andrew Purtell <apurtell@apache.org>
> >> wrote:
> >>>
> >>>> I meant this to say "a few really large values"
> >>>>
> >>>> On Sun, Jan 6, 2013 at 12:49 PM, Andrew Purtell <apurtell@apache.org=
>
> >>>> wrote:
> >>>>
> >>>>> Consider if the split threshold is 2 GB but your one row contains 1=
0
> >> GB
> >>>> as
> >>>>> really large value.
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Best regards,
> >>>>
> >>>>   - Andy
> >>>>
> >>>> Problems worthy of attack prove their worth by hitting back. - Piet
> Hein
> >>>> (via Tom White)
> >>>>
> >>
> >>
>
>

--14dae9cdc0f373a20104d304f222--