)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"139b518b69e47c841d222b16991cefb134ee82e2","unresolved":false,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Database purge deleted spec"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This spec details the abiltiy to cleanly purge \"deleted\" rows."},{"line_number":10,"context_line":"This provides confirmed data destruction beyond the current"},{"line_number":11,"context_line":"archive_deleted_rows functionality."},{"line_number":12,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"da20952f_8bcbc252","line":9,"updated":"2015-09-05 05:18:56.000000000","message":"s/abiltiy/ability/","commit_id":"b3f40c95cce0efe48f98509a042dd516625c5585"}],"specs/kilo/database-purge.rst":[{"author":{"_account_id":13161,"name":"Kamil Rykowski","email":"kamil.rykowski@gmail.com","username":"krykowski"},"change_message_id":"1960b84257a4db54a53db1cd3a384600a84998b2","unresolved":false,"context_lines":[{"line_number":14,"context_line":""},{"line_number":15,"context_line":"This spec adds the ability to sanely and safely purge deleted rows from"},{"line_number":16,"context_line":"the glance database for all relavent tables. Presently, we keep all deleted"},{"line_number":17,"context_line":"rows, or archive them to a \u0027shadow\u0027 table. I believe this is unmaintainable"},{"line_number":18,"context_line":"as we move towards more upgradable releases. Today, most users depend on"},{"line_number":19,"context_line":"manual DB queries to delete this data, but this opens up to human errors."},{"line_number":20,"context_line":"    "}],"source_content_type":"text/x-rst","patch_set":3,"id":"bab921fb_c2289d35","line":17,"updated":"2015-04-27 08:06:51.000000000","message":"Glance doesn\u0027t use such pattern as shadow tables. The rows are simply marked as deleted, as you have mentioned.","commit_id":"61b4d1bd56d5ec57dde110020f119b40fc09eb34"},{"author":{"_account_id":13161,"name":"Kamil Rykowski","email":"kamil.rykowski@gmail.com","username":"krykowski"},"change_message_id":"1960b84257a4db54a53db1cd3a384600a84998b2","unresolved":false,"context_lines":[{"line_number":17,"context_line":"rows, or archive them to a \u0027shadow\u0027 table. I believe this is unmaintainable"},{"line_number":18,"context_line":"as we move towards more upgradable releases. Today, most users depend on"},{"line_number":19,"context_line":"manual DB queries to delete this data, but this opens up to human errors."},{"line_number":20,"context_line":"    "},{"line_number":21,"context_line":"The goal is to have this be an extention to the `glance-manage db` command."},{"line_number":22,"context_line":"Similar specs are being submitted to all the various projects that touch"},{"line_number":23,"context_line":"a database."}],"source_content_type":"text/x-rst","patch_set":3,"id":"bab921fb_821f4507","line":20,"updated":"2015-04-27 08:06:51.000000000","message":"Extra spaces.","commit_id":"61b4d1bd56d5ec57dde110020f119b40fc09eb34"},{"author":{"_account_id":13161,"name":"Kamil Rykowski","email":"kamil.rykowski@gmail.com","username":"krykowski"},"change_message_id":"1960b84257a4db54a53db1cd3a384600a84998b2","unresolved":false,"context_lines":[{"line_number":36,"context_line":"glance/glance/cmd/manage.py"},{"line_number":37,"context_line":"This will take a number of days argument, and use that for a data_sub match"},{"line_number":38,"context_line":"Like:"},{"line_number":39,"context_line":"delete from instances where deleted !\u003d 0 and deleted_at \u003e data_sub(NOW()...)"},{"line_number":40,"context_line":""},{"line_number":41,"context_line":"Alternatives"},{"line_number":42,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bab921fb_a2e929e8","line":39,"updated":"2015-04-27 08:06:51.000000000","message":"Can you rename it to images to better match the spec for this specific project?","commit_id":"61b4d1bd56d5ec57dde110020f119b40fc09eb34"},{"author":{"_account_id":2537,"name":"Nikhil Komawar","email":"nik.komawar@gmail.com","username":"nikhil-komawar"},"change_message_id":"ffaf2068d1abbc0fec1b9ddb7c418c3864eb893d","unresolved":false,"context_lines":[{"line_number":79,"context_line":""},{"line_number":80,"context_line":"Other deployer impact"},{"line_number":81,"context_line":"---------------------"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"None"},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"Developer impact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"bab921fb_726555b3","line":82,"updated":"2015-04-25 00:51:08.000000000","message":"This affects the operators ability to identify and delete all those rows from the DB that have location stored for backend data entities, that are not (or partially) deleted due to some error at the time of the DELETE api call or during scrubber\u0027s data purge run.","commit_id":"61b4d1bd56d5ec57dde110020f119b40fc09eb34"}],"specs/liberty/database-purge.rst":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e7b9e5b9e37e0c93fa4fa7fed3718d9d0656372c","unresolved":false,"context_lines":[{"line_number":13,"context_line":"https://blueprints.launchpad.net/glance/+spec/database-purge"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"This spec adds the ability to sanely and safely purge deleted rows from"},{"line_number":16,"context_line":"the glance database for all relavent tables. Presently, we keep all deleted"},{"line_number":17,"context_line":"rows. I believe this is unmaintainable as we move towards more upgradable"},{"line_number":18,"context_line":"releases. Today, most users depend on manual DB queries to delete this data,"},{"line_number":19,"context_line":"but this opens up to human errors."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a4dcd0f_e51357b6","line":16,"updated":"2015-08-13 14:26:13.000000000","message":"relevent","commit_id":"2c8e8258c10cdd3cdcd33527f3cd27e49a87cbc9"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e7b9e5b9e37e0c93fa4fa7fed3718d9d0656372c","unresolved":false,"context_lines":[{"line_number":16,"context_line":"the glance database for all relavent tables. Presently, we keep all deleted"},{"line_number":17,"context_line":"rows. I believe this is unmaintainable as we move towards more upgradable"},{"line_number":18,"context_line":"releases. Today, most users depend on manual DB queries to delete this data,"},{"line_number":19,"context_line":"but this opens up to human errors."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"The goal is to have this be an extention to the `glance-manage db` command."},{"line_number":22,"context_line":"Similar specs are being submitted to all the various projects that touch"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a4dcd0f_05cc4333","line":19,"updated":"2015-08-13 14:26:13.000000000","message":"maybe change \"this opens up\" to \"this exposes the DB to\"","commit_id":"2c8e8258c10cdd3cdcd33527f3cd27e49a87cbc9"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e7b9e5b9e37e0c93fa4fa7fed3718d9d0656372c","unresolved":false,"context_lines":[{"line_number":68,"context_line":"Other end user impact"},{"line_number":69,"context_line":"---------------------"},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"This affets the operators ability to identify and delete all those rows from"},{"line_number":72,"context_line":"the DB that have location stored for backend data entities, that are not"},{"line_number":73,"context_line":"deleted (or partially deleted) due to some error at the time of the DELETE api"},{"line_number":74,"context_line":"call or during scrubber\u0027s data purge run."}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a4dcd0f_65b2e795","line":71,"updated":"2015-08-13 14:26:13.000000000","message":"\"affects\" and \"operator\u0027s\"","commit_id":"2c8e8258c10cdd3cdcd33527f3cd27e49a87cbc9"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"e7b9e5b9e37e0c93fa4fa7fed3718d9d0656372c","unresolved":false,"context_lines":[{"line_number":133,"context_line":"Documentation Impact"},{"line_number":134,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":135,"context_line":""},{"line_number":136,"context_line":"will need to add documentation of this feature"},{"line_number":137,"context_line":""},{"line_number":138,"context_line":"References"},{"line_number":139,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a4dcd0f_985436fe","line":136,"updated":"2015-08-13 14:26:13.000000000","message":"The documentation needs to emphasize that the image_locations table will be trimmed, which will destroy all information about where the image was stored in various backends.  The operator should keep this in mind when selecting the number-of-days value for the purge function.","commit_id":"2c8e8258c10cdd3cdcd33527f3cd27e49a87cbc9"},{"author":{"_account_id":15054,"name":"wangxiyuan","email":"wangxiyuan1007@gmail.com","username":"wangxiyuan"},"change_message_id":"60e46d1629ee23177a6e1b2be185d4510730f3e5","unresolved":false,"context_lines":[{"line_number":13,"context_line":"https://blueprints.launchpad.net/glance/+spec/database-purge"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"This spec adds the ability to sanely and safely purge deleted rows from"},{"line_number":16,"context_line":"the glance database for all relevant tables. Presently, we keep all deleted"},{"line_number":17,"context_line":"rows. I believe this is unmaintainable as we move towards more upgradable"},{"line_number":18,"context_line":"releases. Today, most users depend on manual DB queries to delete this data,"},{"line_number":19,"context_line":"but this exposes the DB to human errors."}],"source_content_type":"text/x-rst","patch_set":5,"id":"da20952f_4e984a78","line":16,"updated":"2015-09-06 11:33:40.000000000","message":"Could different models delete rows separately? I mean that User maybe just want delete only image or task or some other object in some case, not delete them all at once.","commit_id":"b3f40c95cce0efe48f98509a042dd516625c5585"},{"author":{"_account_id":13997,"name":"SHIGEMATSU Mitsuhiro","email":"shigematsu.mitsuhiro@lab.ntt.co.jp","username":"pshige"},"change_message_id":"139b518b69e47c841d222b16991cefb134ee82e2","unresolved":false,"context_lines":[{"line_number":26,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Very long lived Openstack installations will carry around database rows"},{"line_number":29,"context_line":"for years and years. To date, there is no \"mechanism\" to programatically"},{"line_number":30,"context_line":"purge the deleted data. The archive rows feature doesn\u0027t solve this."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":5,"id":"da20952f_6bbe6eaf","line":29,"updated":"2015-09-05 05:18:56.000000000","message":"s/programatically/programmatically/","commit_id":"b3f40c95cce0efe48f98509a042dd516625c5585"}]}