)]}'
{"keystone/common/config.py":[{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"0c08b1264557d1b5162a6da4832a9a09fcaae98d","unresolved":false,"context_lines":[{"line_number":526,"context_line":"                        \u0027the keystone.endpoint_policy namespace.\u0027),"},{"line_number":527,"context_line":"    ],"},{"line_number":528,"context_line":"    \u0027sql\u0027: ["},{"line_number":529,"context_line":"        cfg.BoolOpt(\u0027backward_compatible\u0027,"},{"line_number":530,"context_line":"                    default\u003dTrue,"},{"line_number":531,"context_line":"                    help\u003d\u0027Flag used in rolling upgrades of SQL databases. You \u0027"},{"line_number":532,"context_line":"                         \u0027can set this flag to False only after running the \u0027"}],"source_content_type":"text/x-python","patch_set":3,"id":"9a68dd71_91f94550","line":529,"updated":"2016-01-20 19:49:20.000000000","message":"I am 100% against adding in options like this. We can\u0027t ever make it default False and no one except edge cases will opt in to it. This \"fix\" still feels like a change for speculative benefits.\n\nIf we are doing this we should be looking at how we can handle the current uses while maintaining the efficiency gains. I also would like to have clear proof of these efficiency gains. \n\nSorry to be hard on this proposal but I\u0027m not convinced this is a win due to both added complexity and the relative edge case it is solving. The tokens being stored in the DB is soon to be the non-recommended method, moving to Fernet removes the bulk of data that keystone has to manage in the DB. I would rather see focus on the rolling schema migrations and other SQL-specific [fix the joins, stop hitting the db 400000 times for the same object in the same request] than muck with the datatypes in the schema for the sake of minor index efficiency gains and minor storage gains.","commit_id":"7edc169e4384c8ac9cf34cdaef60c5d8be9c68dd"},{"author":{"_account_id":17860,"name":"Samuel de Medeiros Queiroz","email":"samueldmq@gmail.com","username":"samueldmq"},"change_message_id":"48f46f0c976edca309b6b2f7a2c4cdb0aa60a632","unresolved":false,"context_lines":[{"line_number":526,"context_line":"                        \u0027the keystone.endpoint_policy namespace.\u0027),"},{"line_number":527,"context_line":"    ],"},{"line_number":528,"context_line":"    \u0027sql\u0027: ["},{"line_number":529,"context_line":"        cfg.BoolOpt(\u0027backward_compatible\u0027,"},{"line_number":530,"context_line":"                    default\u003dTrue,"},{"line_number":531,"context_line":"                    help\u003d\u0027Flag used in rolling upgrades of SQL databases. You \u0027"},{"line_number":532,"context_line":"                         \u0027can set this flag to False only after running the \u0027"}],"source_content_type":"text/x-python","patch_set":3,"id":"7aa08908_15670126","line":529,"in_reply_to":"9a68dd71_91f94550","updated":"2016-06-07 13:54:35.000000000","message":"Agreed","commit_id":"7edc169e4384c8ac9cf34cdaef60c5d8be9c68dd"}]}