Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <BLU0-SMTP199D40A581304F1CCAC732F80850@phx.gbl>
References: <BLU0-SMTP199D40A581304F1CCAC732F80850@phx.gbl>
Date: Wed, 3 Oct 2012 16:53:52 +0200
Message-ID: 
 <CADK=YxsTS+RcAXL8LmRho+QXEqzY71_GR1=CEwr8wi9LaZX36w@mail.gmail.com>
Subject: Re: HBASE vs Data Historian
From: Damien Hardy <dhardy@viadeoteam.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=047d7b2ee13ba56e7104cb28ceda

--047d7b2ee13ba56e7104cb28ceda
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hello,

Take a look at http://opentsdb.net/overview.html it's really look like what
your are describing.

Cheers

2012/10/3 Wendy Buster <stevebuster911@hotmail.com>

> I use a data historian (sometimes called time series database) for
> collecting and persisting large (billions) of rows of  measurement data.
>  The data being collected is off of a manufacturing equipment and
> represents sensors such as temperature, pressure=85.  I've been wondering=
 if
> I should be researching some type of BigData replacement.  The historian
> simply stores key=3Dvalue types data, primarily made up of timestamp=3Dva=
lue.
>  At 3:00, temperature was 40, at 3:01, it was 40=85. Lots of repetitive d=
ata,
> but historians are good at compression, but cost $$.  I have to believe
> that commodity hardware is a lot less than year over year software
> maintenance.  Has anyone used any of the Apache Hadoop products in this
> scenario?
>
> Thanks
>
>


--=20
Damien

--047d7b2ee13ba56e7104cb28ceda--