Return-Path: 
 <user-return-44599-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-user-archive@www.apache.org
Delivered-To: apmail-hbase-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 8EE80118E9
	for <apmail-hbase-user-archive@www.apache.org>;
 Fri,  8 Aug 2014 07:47:32 +0000 (UTC)
Received: (qmail 92880 invoked by uid 500); 8 Aug 2014 07:47:31 -0000
Delivered-To: apmail-hbase-user-archive@hbase.apache.org
Received: (qmail 92806 invoked by uid 500); 8 Aug 2014 07:47:30 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Received: (qmail 92794 invoked by uid 99); 8 Aug 2014 07:47:30 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Aug 2014 07:47:30 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of serega.sheypak@gmail.com
 designates 209.85.217.180 as permitted sender)
Received: from [209.85.217.180] (HELO mail-lb0-f180.google.com)
 (209.85.217.180)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Aug 2014 07:47:25 +0000
Received: by mail-lb0-f180.google.com with SMTP id v6so3567391lbi.11
        for <user@hbase.apache.org>; Fri, 08 Aug 2014 00:47:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=T7nP3NGGG4NLVVDlDAUp62EjAdI6SZ1aTEqFGaEwGrQ=;
        b=lITrYVh/j0KsIQfrKvsigdjCaqBROou9WzX7+LWJCzzbPA6it5ljfE9r7hl85UZTYU
         ePE2eeQL7dnLFEPNWT10j5n0LyYnA9u6SSjpK2fHuuxm7AXHJw0zKUS6EZrVEPfWewC6
         5fkArkSogqMPDEDAnq361hIhDEKUAmN2Llf4i5N3JSHUJolZh43pS3lfDy39UkSo7oDZ
         t1SWNti1rqJYR3pB5rMEZ6ZnMjDX8NPPSxGCkHvXXjV2/+tZjjDqEHZ1VD8afw7AY0E0
         jczlsDg3YjctdKZQbxcYivg5ogIkLIVASGOo684uUd1S6tPLKzZYxn2hL2Tks6ktTUfX
         3NtQ==
X-Received: by 10.152.171.69 with SMTP id as5mr15365lac.94.1407484023246; Fri,
 08 Aug 2014 00:47:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.146.134 with HTTP; Fri, 8 Aug 2014 00:46:43 -0700 (PDT)
From: Serega Sheypak <serega.sheypak@gmail.com>
Date: Fri, 8 Aug 2014 11:46:43 +0400
Message-ID: 
 <CABNOTEVgFAg6w7VA3edbeR=Q5ePFOfZffOQ_Cdt=koUjWPXUaw@mail.gmail.com>
Subject: serving static images using HBase
To: user <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=001a1134daee3b946005001969c6
X-Virus-Checked: Checked by ClamAV on apache.org

--001a1134daee3b946005001969c6
Content-Type: text/plain; charset=UTF-8

Hi, we have 10^8 small jpg/png images each size is 20-100 Kb. They are
thumbs.
These images are used in many web-sites as static content.
Is it good Idea to place them to HBase and serve to users?

right now all images are on SSD discs with complicated partitioning and
backup procedures. It becomes hard to maintain them because qtty and total
size of images grow.

--001a1134daee3b946005001969c6--