)]}'
{"ceilosca/ceilometer/storage/impl_monasca.py":[{"author":{"_account_id":13560,"name":"Rohit Jaiswal","email":"rohit.jaiswal@gmail.com","username":"rjaiswal"},"change_message_id":"645dda8be25640bab17a82611bd564580ea0fd1a","unresolved":false,"context_lines":[{"line_number":222,"context_line":"                    m \u003d self._convert_to_dict("},{"line_number":223,"context_line":"                        sample[\u0027measurements\u0027][0], sample[\u0027columns\u0027])"},{"line_number":224,"context_line":"                    vm \u003d m[\u0027value_meta\u0027]"},{"line_number":225,"context_line":"                    if not self._match_metaquery_to_value_meta(q, vm):"},{"line_number":226,"context_line":"                        continue"},{"line_number":227,"context_line":"                    if d.get(\u0027resource_id\u0027):"},{"line_number":228,"context_line":"                        yield api_models.Resource("}],"source_content_type":"text/x-python","patch_set":2,"id":"1a4dcd0f_3c60d600","line":225,"updated":"2015-08-11 21:44:16.000000000","message":"This will just try to match value-meta of a single measurement (of a matched metric) with the metaquery input, Should this be done for all measurements of a metric before continuing to the next metric? Let me know if i missed anything.","commit_id":"7cb38f05c0d491a424b3de6ec4a7d52a2d26a44e"},{"author":{"_account_id":12621,"name":"Pauline Yeung","email":"yeungp@cisco.com","username":"yeungp"},"change_message_id":"2c46f2af6f458c447fc7babee03d7af2aac3df79","unresolved":false,"context_lines":[{"line_number":222,"context_line":"                    m \u003d self._convert_to_dict("},{"line_number":223,"context_line":"                        sample[\u0027measurements\u0027][0], sample[\u0027columns\u0027])"},{"line_number":224,"context_line":"                    vm \u003d m[\u0027value_meta\u0027]"},{"line_number":225,"context_line":"                    if not self._match_metaquery_to_value_meta(q, vm):"},{"line_number":226,"context_line":"                        continue"},{"line_number":227,"context_line":"                    if d.get(\u0027resource_id\u0027):"},{"line_number":228,"context_line":"                        yield api_models.Resource("}],"source_content_type":"text/x-python","patch_set":2,"id":"1a4dcd0f_0f959931","line":225,"in_reply_to":"1a4dcd0f_3c60d600","updated":"2015-08-12 01:39:22.000000000","message":"This is a good point.\n It may be due to the current implementation only supports same value_meta for all measurements in one sample. So \u0027m\u0027 or {\u0027timestamp\u0027: TIME, \u0027value\u0027: VALUE, \u0027value_meta\u0027: METADATA} is from the first measurement of a sample or sample[\u0027measurements\u0027][0].\n This should be changed to check value_meta for all measurements in one sample when retrieve resource information below also supports different value_meta in each measurement per sample.","commit_id":"7cb38f05c0d491a424b3de6ec4a7d52a2d26a44e"}]}