How does HBase compare to Hive when it comes to dynamic data sets ?
Does Hive support multi version concurrency control ? I am new to
Hadoop, hence trying to get an idea of how to evaluate these different
technologies and provide concrete justifications on why to choose one
over the other.
Also
and then another table where you can use the same unique key and create
>> columns with column names of time stamps with the state as the value.
>>
>> HTH
>>
>> -Mike
>>
>>
>>
>>> Date: Wed, 13 Apr
is one table of immutable attributes, with a unique
> key, and then another table where you can use the same unique key and create
> columns with column names of time stamps with the state as the value.
>
> HTH
>
> -Mike
>
>
> --------
HTH
-Mike
> Date: Wed, 13 Apr 2011 18:12:58 -0700
> Subject: Dynamic Data Sets
> From: selek...@yahoo.com
> To: common-user@hadoop.apache.org
>
> I have a requirement where I have large sets of incoming data into a
> system I own.
>
> A single unit of da
Hbase is very good at this kind of thing.
Depending on your aggregation needs OpenTSDB might be interesting since they
store and query against large amounts of time ordered data similar to what
you want to do.
It isn't clear to whether your data is primarily about current state or
about time-embe
I have a requirement where I have large sets of incoming data into a
system I own.
A single unit of data in this set has a set of immutable attributes +
state attached to it. The state is dynamic and can change at any time.
What is the best way to run analytical queries on data of such nature
?
O
