)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6928,"name":"Ben Nemec","email":"openstack@nemebean.com","username":"bnemec"},"change_message_id":"857d148596a62c3f7ff1ff7d55693d76241a0110","unresolved":false,"context_lines":[{"line_number":14,"context_line":"which instead stores each database table in its own file, each of"},{"line_number":15,"context_line":"which is also shrinkable by the InnoDB engine."},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Fixes-bug: #1660722"},{"line_number":18,"context_line":"Change-Id: I59ee53f6462a2eeddad72b1d75c77a69322d5de4"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a461143_fb33bf11","line":17,"updated":"2017-01-31 18:21:59.000000000","message":"Nit: Closes-Bug is the documented tag, but this will accomplish the same thing.","commit_id":"d5d96e69e3a1a166524762ec70b054342ccd1e68"}],"releasenotes/notes/innodb_file_per_table-f925b3bbf29d44ea.yaml":[{"author":{"_account_id":11816,"name":"mike_mp@zzzcomputing.com","display_name":"Mike Bayer","email":"mike_mp@zzzcomputing.com","username":"zzzeek","status":"Red Hat"},"change_message_id":"bc728b5627f1469dec00eb30334421312d0f0e4e","unresolved":false,"context_lines":[{"line_number":2,"context_line":"features:"},{"line_number":3,"context_line":"  - Enable innodb_file_per_table for MySQL/MariaDB databases"},{"line_number":4,"context_line":"upgrade:"},{"line_number":5,"context_line":"  - |"},{"line_number":6,"context_line":"    Newly created MySQL database tables will be stored in their own datafiles,"},{"line_number":7,"context_line":"    instead of in a single monolithic ibdata file."},{"line_number":8,"context_line":"  - |"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"3a461143_67d9c983","line":5,"updated":"2017-02-01 17:03:14.000000000","message":"this is the \"verbose\" version with everything relevant to upgrading.   can remove this if we feel this information should be handled elsewhere.","commit_id":"e9a739f7dd7ed754ec2892f36f1601271c4d46a3"},{"author":{"_account_id":20778,"name":"Damien Ciabrini","email":"dciabrin@redhat.com","username":"dciabrin"},"change_message_id":"fe1d0d8faceecca30b88310fe0a1ba2f4dd0c717","unresolved":false,"context_lines":[{"line_number":5,"context_line":"  - |"},{"line_number":6,"context_line":"    Newly created MySQL database tables will be stored in their own datafiles,"},{"line_number":7,"context_line":"    instead of in a single monolithic ibdata file."},{"line_number":8,"context_line":"  - |"},{"line_number":9,"context_line":"    Existing MySQL database tables that are persisted within the monolithic"},{"line_number":10,"context_line":"    ibdata file will remain so, unless the database is dumped and restored,"},{"line_number":11,"context_line":"    or on a per-table basis by running the MySQL command"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"3a461143_249ed807","line":8,"updated":"2017-02-01 20:02:13.000000000","message":"Galera-specific: while \"new tables being created in their own datafiles\" if perfectly fine, I think we should make it clear not to upgrade a galera cluster with the instruction given below. \n\n\"If galera is enabled, do not mix a node which have been dumped/restored with other nodes still relying on one ibdata. This will break SST.\"\n\nAlso, running alter table on big tables may be too big for the max writeset size (wsrep_max_ws_size) and cause all sort of data issues.","commit_id":"e9a739f7dd7ed754ec2892f36f1601271c4d46a3"}]}