Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
Description
To test S3 Storage engine the following main steps should be performed:
1. Install libcurl and libxml2-devel libs.
2. Build MariaDB from the `maria-s3` repository in the mariadb server repo.
3. Run mysql-test/mtr-aws for `s3` suite.
4. Run `s3.no_s3` as usual mtr.
Additional tasks:
- Create more tests for s3.
- Do test with big tables.
- Run complex queries with join with 2,3,4 tables.
- Do self joins.
- Test replication when table is created in s3 and data is read from s3. In this case the data is 'shared' so the slave should just instantiate the table, not create it.
Attachments
Issue Links
- relates to
-
MDEV-19461
Assertion failure upon altering temporary S3 table
-
- Closed
-
-
MDEV-20834 Engine cannot be altered to S3 from MyISAM for a 110Gb table.
-
- Stalled
-
-
-
- Closed
-
-
MDEV-19463
Altering sequence to S3 leaves unremovable garbage behind
-
- Closed
-
-
MDEV-19464
Altering partitioned table into S3 causes an obscure error
-
- Closed
-
-
MDEV-19465
Server crashes in s3_block_read upon IN query
-
- Closed
-
-
MDEV-19466
Syntax error in the error message: Expected object ... didn't exists
-
- Closed
-
-
MDEV-19575
Assertion `page_st == 1' failed upon SELECT from S3 table which is being converted into Aria
-
- Closed
-
-
MDEV-19585
Assertion `!is_set() || (m_status == DA_OK_BULK && is_bulk_op())' failed upon SELECT from S3 table with concurrent BACKUP stage
-
- Closed
-
-
MDEV-19591
Assertion `!table->pos_in_locked_tables' failed in tc_release_table upon altering table into S3 under lock
-
- Closed
-
