ARCHIVE not enabled by default on MariaDB 10.1
My strong advice to you would be to change the tables to be anything but ARCHIVE. Even InnoDB would be fine and preferred over ARHCIVE. We've had a number of sites have their entire audit schema's become corrupt and its been down to the storage engine being ARCHIVE.

Also you'll probably want to add indexes into the audit schema otherwise you cant access the change log without waiting for minutes.

I think later versions of CiviCRM do not use ARCHIVE storage format by default