)]}'
{"ceilometer/storage/impl_hbase.py":[{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"fd6a8e6eb825a53ab9152aeaa0b8dcab1fc70f07","unresolved":false,"context_lines":[{"line_number":177,"context_line":"            # Rowkey consists of reversed timestamp, meter and a"},{"line_number":178,"context_line":"            # message uuid for purposes of uniqueness"},{"line_number":179,"context_line":"            row \u003d hbase_utils.prepare_key(data[\u0027counter_name\u0027], rts,"},{"line_number":180,"context_line":"                                          data[\u0027message_id\u0027])"},{"line_number":181,"context_line":"            record \u003d hbase_utils.serialize_entry("},{"line_number":182,"context_line":"                data, **{\u0027source\u0027: data[\u0027source\u0027], \u0027rts\u0027: rts,"},{"line_number":183,"context_line":"                         \u0027message\u0027: data, \u0027recorded_at\u0027: timeutils.utcnow()})"}],"source_content_type":"text/x-python","patch_set":1,"id":"bab921fb_65bcdf6c","line":180,"updated":"2015-04-23 09:25:36.000000000","message":"Can we just unilaterally change the row key here?\n\nHow does that impact on pre-existing datastores?","commit_id":"f5b994829bbd19794eba062ea79599f3b78a9286"},{"author":{"_account_id":2284,"name":"Eoghan Glynn","email":"eglynn@redhat.com","username":"eglynn"},"change_message_id":"e89cc423cf37e87c4ac106847e3591e2096fa988","unresolved":false,"context_lines":[{"line_number":177,"context_line":"            # Rowkey consists of reversed timestamp, meter and a"},{"line_number":178,"context_line":"            # message uuid for purposes of uniqueness"},{"line_number":179,"context_line":"            row \u003d hbase_utils.prepare_key(data[\u0027counter_name\u0027], rts,"},{"line_number":180,"context_line":"                                          data[\u0027message_id\u0027])"},{"line_number":181,"context_line":"            record \u003d hbase_utils.serialize_entry("},{"line_number":182,"context_line":"                data, **{\u0027source\u0027: data[\u0027source\u0027], \u0027rts\u0027: rts,"},{"line_number":183,"context_line":"                         \u0027message\u0027: data, \u0027recorded_at\u0027: timeutils.utcnow()})"}],"source_content_type":"text/x-python","patch_set":1,"id":"bab921fb_2026d568","line":180,"in_reply_to":"bab921fb_65bcdf6c","updated":"2015-04-23 09:36:57.000000000","message":"From _nadya_ ...\n\neglynn: we don\u0027t need it. We use some uuid or message_id only to provide uniqueness. It is not used in queries. The row key consists of reversed timestamp, meter and a message uuid. When we scan table we filter by timestamps and meter names. The result is a set of \"meters\" (samples actually) and all of them should have different \u0027postfix\u0027 in row keys to be stored. If a row-key are the same HBase will rewrite an entry. So we don\u0027t care about postfix\u0027s value, we only need it to be as unique as possible","commit_id":"f5b994829bbd19794eba062ea79599f3b78a9286"}]}