Constructing structure of events in HBase
The purpose of this bp is to construct convenient structure of event's storage in HBase.
Proposed preliminary structure of Events in HBase:
table: Events
- rowkey: event_id + reversed_timestamp
- column: event_type => string with description of event
- [list of columns: trait_id + trait_desc + trait_type=> trait_data]
Structure that is proposed will support next queries:
- event’s generation time
- event id
- event type
- trait: id, description, type
Blueprint information
- Status:
- Complete
- Approver:
- Nadya Privalova
- Priority:
- Undefined
- Drafter:
- Igor Degtiarov
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- Proposed for juno
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
- Nadya Privalova
Related branches
Related bugs
Sprints
Whiteboard
The main idea is to find out all possible relationships between data that are stored inside Event metric. According to this relations and tasks of filtering stored data it will become clear what structure of Event model in Hbase will be the most convenient.
Question (nprivalova): Why do we need a separate blueprint? https:/
Answer (idegtiarov): I thought it was a good idea to discuss separately all queries that is necessary for Events. This discussion or research may be very useful for Events implementation on other backends. The purpose is to try to collect all possible queries for Events, and after that correct proposed Event structure on HBase.
What do you think about it?
