)]}'
{"doc/source/cli/nova-manage.rst":[{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"2a5af8bc3aa117fa35e0d3b4b12459a18d9acba9","unresolved":false,"context_lines":[{"line_number":62,"context_line":""},{"line_number":63,"context_line":"``nova-manage db archive_deleted_rows [--max_rows \u003cnumber\u003e] [--verbose] [--until-complete]``"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"    Move deleted rows from production tables to shadow tables. Note that the"},{"line_number":66,"context_line":"    corresponding rows in the instance_mappings and request_specs tables of the"},{"line_number":67,"context_line":"    API database are purged as well. Specifying --verbose will print the results"},{"line_number":68,"context_line":"    of the archive operation for any tables that were changed. Specifying"},{"line_number":69,"context_line":"    --until-complete will make the command run continuously until all deleted rows"},{"line_number":70,"context_line":"    are archived. Use the --max_rows option, which defaults to 1000, as a batch"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df7087c5_89aa0e83","line":67,"range":{"start_line":65,"start_character":63,"end_line":67,"end_character":36},"updated":"2018-03-07 21:02:44.000000000","message":"I would try to tie in some wording about how we only do this if instances were archived. So either something like:\n\n\"Note that if any instance records are archived, the corresponding rows in the instance_mappings and request_specs tables of the API database are purged as well\"\n\nor\n\n\"Note that the corresponding rows in the instance_mappings and request_specs tables of the API database are purged when instance records are archived.\"\n\nIt\u0027s the \"as well\" part, without context to the instance records, that trips me up.","commit_id":"8b4337eddb7105e055e5f663cdc7028b3b8a270d"},{"author":{"_account_id":26936,"name":"Surya Seetharaman","email":"suryaseetharaman.9@gmail.com","username":"tssurya"},"change_message_id":"4cb4e547b1c9de5e40148ab99f13edca66f68d2f","unresolved":false,"context_lines":[{"line_number":62,"context_line":""},{"line_number":63,"context_line":"``nova-manage db archive_deleted_rows [--max_rows \u003cnumber\u003e] [--verbose] [--until-complete]``"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"    Move deleted rows from production tables to shadow tables. Note that the"},{"line_number":66,"context_line":"    corresponding rows in the instance_mappings and request_specs tables of the"},{"line_number":67,"context_line":"    API database are purged as well. Specifying --verbose will print the results"},{"line_number":68,"context_line":"    of the archive operation for any tables that were changed. Specifying"},{"line_number":69,"context_line":"    --until-complete will make the command run continuously until all deleted rows"},{"line_number":70,"context_line":"    are archived. Use the --max_rows option, which defaults to 1000, as a batch"}],"source_content_type":"text/x-rst","patch_set":1,"id":"df7087c5_daed2626","line":67,"range":{"start_line":65,"start_character":63,"end_line":67,"end_character":36},"in_reply_to":"df7087c5_89aa0e83","updated":"2018-03-07 23:28:42.000000000","message":"Done","commit_id":"8b4337eddb7105e055e5f663cdc7028b3b8a270d"}]}