[MDEV-19867] fix mysqldump to by default not copy S3 tables Created: 2019-06-26  Updated: 2023-11-22  Resolved: 2019-07-01

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - S3
Fix Version/s: 10.5.0

Type: Task Priority: Major
Reporter: Vladislav Lesin Assignee: Vladislav Lesin
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Duplicate
PartOf
is part of MDEV-17841 S3 Storage engine Closed
Relates
relates to MDEV-19887 Document --copy_s3_tables option on m... Closed

 Description   

There should be two options when coping S3 tables with mysqldump (should be a startup option --copy_s3_tables, boolean, default no)
1) Ignore all tables with engine S3, as the data is already safe in S3 and any computer where you restore the backup will automatically discover the S3 table.
2) Copy the table as a normal table with the following 2 changes:

  • Change ENGINE=S3 to ENGINE=ARIA;
  • After copy add to log 'ALTER TABLE table_name ENGINE=S3'

 Comments   
Comment by Vladislav Lesin [ 2019-06-26 ]

https://github.com/vlad-lesin/mariadb-server/tree/bb-10.5-MENT-72-mysqldump
https://buildbot.askmonty.org/buildbot/grid?category=main&branch=bb-10.5-MENT-72-mysqldump

Generated at Thu Feb 08 08:54:58 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.