[MDEV-13827] Add encryption tests for FULLTEXT INDEX Created: 2017-09-17 Updated: 2023-04-12 Resolved: 2023-04-11 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.1, 10.2 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | Marko Mäkelä | Assignee: | Marko Mäkelä |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Description |
|
As noted in This was uncaught, because there are no encryption tests for FULLTEXT INDEX whatsoever. I manually checked that the auxiliary tables are encrypted by applying this patch:
After the test failed due to the intentional typo, I checked with
that the internally created tables are encrypted. I also manually checked some files to ensure that they are not empty. This should be done properly by extending the test.
This is obviously not sufficient; similar to my change to innodb.innodb-index-online and innodb.innodb-table-online we should ensure that on successful operation, the amount of encrypted blocks equals the amount of decrypted blocks, and that when encryption is used, some encrypted blocks are being read and written. |
| Comments |
| Comment by Marko Mäkelä [ 2023-04-11 ] |
|
I see that some test was added in Because FLUSH TABLES…FOR EXPORT will not work on InnoDB tables that contain FULLTEXT INDEX, it is a bit tricky to check that the data is actually encrypted. I think that we can live without this extra check in the encryption test suite. |