)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"74dee75490f87eba06b72c3b6a4812231f7668bc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"7d8a57a4_3ff6764f","updated":"2025-06-02 06:50:22.000000000","message":"Thank you!\n\nThe additional storage driver does not change the existing behavior, and only adds another storage v2 backend.","commit_id":"fe2501fbbf796b089d81f7ebfcefdf2125d9953a"},{"author":{"_account_id":28356,"name":"Rafael Weingartner","email":"rafael@apache.org","username":"rafaelweingartner"},"change_message_id":"5a5395ce0817da93dfda4433c52e1ad9fc2080f1","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"b96991e2_41e1206d","updated":"2025-06-23 13:37:08.000000000","message":"Thanks for proposing a new storage backend for CloudKitty!\n\nI have a question. Regarding the summary API [1]. Do you plan to support \"custom_fields\"? Which parts of the CloudKitty API is this new driver going to support?\n\n[1] https://docs.openstack.org/cloudkitty/latest/api-reference/v2/index.html#get-a-rating-summary.","commit_id":"fe2501fbbf796b089d81f7ebfcefdf2125d9953a"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"af2b967b34002156d106bc7f1da7b89b5d25ed41","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"f9e740b9_98e27753","in_reply_to":"b96991e2_41e1206d","updated":"2025-06-27 07:51:57.000000000","message":"I will work on adding support for the reprocessing API, which is missing. Regarding custom_fields, it is curently unsupported because I was aiming at feature parity with Opensearch, which does not support custom_fields.","commit_id":"fe2501fbbf796b089d81f7ebfcefdf2125d9953a"},{"author":{"_account_id":28356,"name":"Rafael Weingartner","email":"rafael@apache.org","username":"rafaelweingartner"},"change_message_id":"f9fc980e933d02305e26f157794344213cf849c2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"3136423c_4828606e","in_reply_to":"e0e9f233_a6cb09f8","updated":"2025-07-04 00:32:29.000000000","message":"For sure, but we need to make this clear in the spec. Right now, we do not see the limitation of the spec. Meaning, it feels like everything is going to be compatible, but that is not the case, right?","commit_id":"fe2501fbbf796b089d81f7ebfcefdf2125d9953a"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"a978d5fc0dec2f8cab33f88b6f54512b65a79c05","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"e0e9f233_a6cb09f8","in_reply_to":"f9e740b9_98e27753","updated":"2025-06-27 07:57:00.000000000","message":"Sorry, I hit Reply before I finished the above comment.\n\nI was saying I was aiming at feature parity with OpenSearch, which does not support custom_fields. Is this a reasonable expectation? Would it be considered for merge once the reprocessing API support is introduced and allow for introducing custom_fields in a subsequent patch?\n\nThank you very much for your attention.","commit_id":"fe2501fbbf796b089d81f7ebfcefdf2125d9953a"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"7c11aecc6c1bfe82caaca6cfd7e26d8bffccfdb3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":3,"id":"8c7bf588_9b89c601","updated":"2025-07-01 09:23:16.000000000","message":"If there is nothing against this proposal spec, I suggest to get it approved and continue the technical and implementation details discussion on the implementation patch.\n\nWhat do you think?","commit_id":"3c5a03014804829c9b5c0d0ba2d32b0325bb9368"},{"author":{"_account_id":28356,"name":"Rafael Weingartner","email":"rafael@apache.org","username":"rafaelweingartner"},"change_message_id":"3dfede7b12cdac12b7dd4e02dcb7106b801cb109","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"16cf74fe_98b6be50","updated":"2025-07-16 06:20:07.000000000","message":"I are operating like this for years now with success. Sometimes, it takes a while for some patches to get merged, even from other CR as me or Pierre. However, it has been ok so far.\n\nI guess, next Monday we will discuss this patch again.","commit_id":"3949206020d6066ee8d87f4e60816c83331d0050"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"3304c9f3efd0b7bdaeecdcdd57f758c5421ab9a2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"63639c23_10db333a","updated":"2025-07-09 06:32:18.000000000","message":"Thank you, since this now has a +2, can we get another and +W to proceed?","commit_id":"3949206020d6066ee8d87f4e60816c83331d0050"},{"author":{"_account_id":4264,"name":"Matthias Runge","email":"mrunge@redhat.com","username":"mrunge"},"change_message_id":"61c05971a09868803e8460693a98f5cf1e8718cd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"86b47ebb_9a195320","in_reply_to":"5072a46d_14f139fa","updated":"2025-07-16 04:35:32.000000000","message":"That\u0027s how OpenStack works, yes.\n\nDoes CloudKitty need more core reviewers then? I\u0027ve seen small projects in the past lift the 2 core reviews requirements in order to proceed.","commit_id":"3949206020d6066ee8d87f4e60816c83331d0050"},{"author":{"_account_id":28356,"name":"Rafael Weingartner","email":"rafael@apache.org","username":"rafaelweingartner"},"change_message_id":"c3f634370c48172b1c4c2b078b57e03bef374a23","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"5072a46d_14f139fa","in_reply_to":"63639c23_10db333a","updated":"2025-07-09 10:46:05.000000000","message":"We need other CR to review it. Then, we can merge it as well.","commit_id":"3949206020d6066ee8d87f4e60816c83331d0050"}],"specs/flamingo/add_v2_storage_driver_for_loki.rst":[{"author":{"_account_id":28356,"name":"Rafael Weingartner","email":"rafael@apache.org","username":"rafaelweingartner"},"change_message_id":"5a5395ce0817da93dfda4433c52e1ad9fc2080f1","unresolved":true,"context_lines":[{"line_number":13,"context_line":"Problem Description"},{"line_number":14,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Cloudkitty currently offers robust integration with several storage backends, "},{"line_number":17,"context_line":"namely Elasticsearch, OpenSearch, and InfluxDB. While these systems are "},{"line_number":18,"context_line":"powerful and suitable for various data storage and querying needs, their "},{"line_number":19,"context_line":"operational characteristics and resource footprints present challenges for "}],"source_content_type":"text/x-rst","patch_set":2,"id":"656902a3_7143bb86","line":16,"range":{"start_line":16,"start_character":77,"end_line":16,"end_character":78},"updated":"2025-06-23 13:37:08.000000000","message":"Trailing spaces, can you remove them?","commit_id":"fe2501fbbf796b089d81f7ebfcefdf2125d9953a"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"af2b967b34002156d106bc7f1da7b89b5d25ed41","unresolved":false,"context_lines":[{"line_number":13,"context_line":"Problem Description"},{"line_number":14,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":15,"context_line":""},{"line_number":16,"context_line":"Cloudkitty currently offers robust integration with several storage backends, "},{"line_number":17,"context_line":"namely Elasticsearch, OpenSearch, and InfluxDB. While these systems are "},{"line_number":18,"context_line":"powerful and suitable for various data storage and querying needs, their "},{"line_number":19,"context_line":"operational characteristics and resource footprints present challenges for "}],"source_content_type":"text/x-rst","patch_set":2,"id":"b0106eb2_489f2bd8","line":16,"range":{"start_line":16,"start_character":77,"end_line":16,"end_character":78},"in_reply_to":"656902a3_7143bb86","updated":"2025-06-27 07:51:57.000000000","message":"Acknowledged","commit_id":"fe2501fbbf796b089d81f7ebfcefdf2125d9953a"},{"author":{"_account_id":28356,"name":"Rafael Weingartner","email":"rafael@apache.org","username":"rafaelweingartner"},"change_message_id":"f9fc980e933d02305e26f157794344213cf849c2","unresolved":true,"context_lines":[{"line_number":33,"context_line":"designed to solve."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"Proposed Change"},{"line_number":37,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"The proposed change will add a new v2 storage backend option for dataframes,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"d7b7d9aa_9fef25a4","line":36,"updated":"2025-07-04 00:32:29.000000000","message":"Is there any API affected here? Will the reprocessing work?\n\nWil the \"custom_fields\" from the \"\n/v2/summary\" endpoint work?","commit_id":"3c5a03014804829c9b5c0d0ba2d32b0325bb9368"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"e03173be3d5669e805fdbc53fc876f772ef2c45a","unresolved":false,"context_lines":[{"line_number":33,"context_line":"designed to solve."},{"line_number":34,"context_line":""},{"line_number":35,"context_line":""},{"line_number":36,"context_line":"Proposed Change"},{"line_number":37,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"The proposed change will add a new v2 storage backend option for dataframes,"}],"source_content_type":"text/x-rst","patch_set":3,"id":"e3f13044_4f951e2d","line":36,"in_reply_to":"d7b7d9aa_9fef25a4","updated":"2025-07-04 09:13:40.000000000","message":"Done, the objective is to achieve feature parity with OpenSearch. That means support all v1 and v2 APIs (including reprocessing) but without custom_fields in the v2 summary endpoint.","commit_id":"3c5a03014804829c9b5c0d0ba2d32b0325bb9368"},{"author":{"_account_id":28356,"name":"Rafael Weingartner","email":"rafael@apache.org","username":"rafaelweingartner"},"change_message_id":"f9fc980e933d02305e26f157794344213cf849c2","unresolved":true,"context_lines":[{"line_number":40,"context_line":"100% compatible with the current options and transparently exchangeable for any"},{"line_number":41,"context_line":"one of the others, but Loki based."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"Moreover, the change only proposes a new option: if the advantages of Loki do"},{"line_number":44,"context_line":"not seem attractive enough for some of our userbase, it also does not force"},{"line_number":45,"context_line":"anyone to switch: the existing options will still be there."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"aaa34843_9372a175","line":43,"updated":"2025-07-04 00:32:29.000000000","message":"these whole paragraph does not seem to propose anything.","commit_id":"3c5a03014804829c9b5c0d0ba2d32b0325bb9368"},{"author":{"_account_id":28356,"name":"Rafael Weingartner","email":"rafael@apache.org","username":"rafaelweingartner"},"change_message_id":"8b98f978c7d6414ed727f81b2c1f6aebadd69533","unresolved":false,"context_lines":[{"line_number":40,"context_line":"100% compatible with the current options and transparently exchangeable for any"},{"line_number":41,"context_line":"one of the others, but Loki based."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"Moreover, the change only proposes a new option: if the advantages of Loki do"},{"line_number":44,"context_line":"not seem attractive enough for some of our userbase, it also does not force"},{"line_number":45,"context_line":"anyone to switch: the existing options will still be there."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"cd42dc29_77c39cd3","line":43,"in_reply_to":"4a2bd6b5_2d072c99","updated":"2025-07-04 12:41:36.000000000","message":"did you push it?","commit_id":"3c5a03014804829c9b5c0d0ba2d32b0325bb9368"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"e03173be3d5669e805fdbc53fc876f772ef2c45a","unresolved":false,"context_lines":[{"line_number":40,"context_line":"100% compatible with the current options and transparently exchangeable for any"},{"line_number":41,"context_line":"one of the others, but Loki based."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"Moreover, the change only proposes a new option: if the advantages of Loki do"},{"line_number":44,"context_line":"not seem attractive enough for some of our userbase, it also does not force"},{"line_number":45,"context_line":"anyone to switch: the existing options will still be there."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"4a2bd6b5_2d072c99","line":43,"in_reply_to":"aaa34843_9372a175","updated":"2025-07-04 09:13:40.000000000","message":"That\u0027s because the redaction is wrong, I wanted to stated that what we are proposing here is just one more storage option. I have rewrited it to make it (hopefully) clearer.","commit_id":"3c5a03014804829c9b5c0d0ba2d32b0325bb9368"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"a5ec0dd585b9ec2cd0bce41048999b0250cd66ca","unresolved":false,"context_lines":[{"line_number":40,"context_line":"100% compatible with the current options and transparently exchangeable for any"},{"line_number":41,"context_line":"one of the others, but Loki based."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"Moreover, the change only proposes a new option: if the advantages of Loki do"},{"line_number":44,"context_line":"not seem attractive enough for some of our userbase, it also does not force"},{"line_number":45,"context_line":"anyone to switch: the existing options will still be there."},{"line_number":46,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"33f41722_1eab9980","line":43,"in_reply_to":"cd42dc29_77c39cd3","updated":"2025-07-04 12:51:57.000000000","message":"Uups, there was a requirement of adding the Signed-off-by that was not needed before and that stopped my push. Now it is done.","commit_id":"3c5a03014804829c9b5c0d0ba2d32b0325bb9368"},{"author":{"_account_id":28356,"name":"Rafael Weingartner","email":"rafael@apache.org","username":"rafaelweingartner"},"change_message_id":"bf97d886c7145cae4a334f940c0e54d7e2d9e7b0","unresolved":true,"context_lines":[{"line_number":16,"context_line":"Cloudkitty currently offers robust integration with several storage backends, "},{"line_number":17,"context_line":"namely Elasticsearch, OpenSearch, and InfluxDB. While these systems are "},{"line_number":18,"context_line":"powerful and suitable for various data storage and querying needs, their "},{"line_number":19,"context_line":"operational characteristics and resource footprints present challenges for "},{"line_number":20,"context_line":"certain deployment scenarios and user ecosystems."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Loki has been positioning itself as a strong contender on the log storage and"}],"source_content_type":"text/x-rst","patch_set":4,"id":"3c69859a_47508f5a","line":19,"range":{"start_line":19,"start_character":74,"end_line":19,"end_character":75},"updated":"2025-07-04 13:10:11.000000000","message":"can you remove the spaces at the end of the lines?","commit_id":"f6a57b6e66058cdc11a97f2a470c59bc77c882e1"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"3ad1da3586768c759a6fe387c9e45c849830b5f0","unresolved":false,"context_lines":[{"line_number":16,"context_line":"Cloudkitty currently offers robust integration with several storage backends, "},{"line_number":17,"context_line":"namely Elasticsearch, OpenSearch, and InfluxDB. While these systems are "},{"line_number":18,"context_line":"powerful and suitable for various data storage and querying needs, their "},{"line_number":19,"context_line":"operational characteristics and resource footprints present challenges for "},{"line_number":20,"context_line":"certain deployment scenarios and user ecosystems."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Loki has been positioning itself as a strong contender on the log storage and"}],"source_content_type":"text/x-rst","patch_set":4,"id":"6b5c0786_28e745e9","line":19,"range":{"start_line":19,"start_character":74,"end_line":19,"end_character":75},"in_reply_to":"3c69859a_47508f5a","updated":"2025-07-04 13:31:06.000000000","message":"Acknowledged","commit_id":"f6a57b6e66058cdc11a97f2a470c59bc77c882e1"},{"author":{"_account_id":28356,"name":"Rafael Weingartner","email":"rafael@apache.org","username":"rafaelweingartner"},"change_message_id":"bf97d886c7145cae4a334f940c0e54d7e2d9e7b0","unresolved":true,"context_lines":[{"line_number":41,"context_line":"it will support the complete set of v1 and v2 APIs but will not have support for "},{"line_number":42,"context_line":"custom_fields in the summary API."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"The change proposed will be optional and no one will be forced to migrate or to use"},{"line_number":45,"context_line":"Loki storage."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The change will include unit tests, a new Zuul job with tempest tests and a"},{"line_number":48,"context_line":"Loki devstack plugin for CI and development needs."}],"source_content_type":"text/x-rst","patch_set":4,"id":"93cbbccc_201baff7","line":45,"range":{"start_line":44,"start_character":0,"end_line":45,"end_character":13},"updated":"2025-07-04 13:10:11.000000000","message":"This sentence does not seem needed. As, it is already state that it is a new option for the storage backend, and not a replacement for the others.","commit_id":"f6a57b6e66058cdc11a97f2a470c59bc77c882e1"},{"author":{"_account_id":32968,"name":"Juan Larriba","email":"jlarriba@redhat.com","username":"jlarriba"},"change_message_id":"3ad1da3586768c759a6fe387c9e45c849830b5f0","unresolved":false,"context_lines":[{"line_number":41,"context_line":"it will support the complete set of v1 and v2 APIs but will not have support for "},{"line_number":42,"context_line":"custom_fields in the summary API."},{"line_number":43,"context_line":""},{"line_number":44,"context_line":"The change proposed will be optional and no one will be forced to migrate or to use"},{"line_number":45,"context_line":"Loki storage."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"The change will include unit tests, a new Zuul job with tempest tests and a"},{"line_number":48,"context_line":"Loki devstack plugin for CI and development needs."}],"source_content_type":"text/x-rst","patch_set":4,"id":"d3888970_40565599","line":45,"range":{"start_line":44,"start_character":0,"end_line":45,"end_character":13},"in_reply_to":"93cbbccc_201baff7","updated":"2025-07-04 13:31:06.000000000","message":"Removed this paragraph, it is true that it is reiterative","commit_id":"f6a57b6e66058cdc11a97f2a470c59bc77c882e1"}]}