Hello,
For today I have prepared a spec for events feature in HBase
https://review.openstack.org/#/c/96417/,
and it was successfully merged. In spec was described the details of event
features in HBase.
Yours,
Igor D.
On Wed, May 21, 2014 at 3:03 PM, Dmitriy Ukhlov dukh...@mirantis.com
wrote:
Hi,
I have found that filter model for Events has mandatory parameters
start_time and end_time
of the events period. So, it seems that structure for rowkey as ''timestamp
+ event_id will be more suitable.
I have started to work on bp
Hello Igor,
Sounds reasonable.
On 05/21/2014 02:38 PM, Igor Degtiarov wrote:
Hi,
I have found that filter model for Events has mandatory parameters
start_time and end_time
of the events period. So, it seems that structure for rowkey as
''timestamp + event_id will be more suitable.
--
Hello Dmitriy!
Of course event_id could identify row. Actually Row structure now is a
question for discuss.
The main feature of HBase that data is stored in sorted rows.
To filter events by time interval we will need to scan all stored data,
when
rowkey is started with event_id. Instead of
Hello Igor!
Could you clarify, please, Why do we need event_id + reversed_timestamp
row key?
Isn't event_id identify row?
On Tue, Apr 29, 2014 at 11:08 AM, Igor Degtiarov idegtia...@mirantis.comwrote:
Hi, everybody.
I’ve started to work on implementation of Event in ceilometer on HBase
