MySQL partition enabled from start

[slartibartfast]

As titles says, what are drawbacks (if any) or cons for not having MySQL partition enabled when installing Zabbix with MySQL support?

Surely, having partitioned tables from the start is the way to have initial Zabbix installation, particularly for beginners which deploy monitoring, learn, and after few months they are hit with either they can't backup it, nor stop it for the backup, or houskeeper process is killing down the server, etc.

Or, if this can't be done with default installation, to implement [Migrate to partitioned mysql tables] button in WebUI.

Thank you

[kloczek]

Only known drawbacks is consequence of changing default database scheme in case of definition of primary keys and indexes on partitioned tables.
In case mayor upgrade if such upgrade will be fiddling around definition of something around those primary keys and indexes it would not possible to embedded into server/proxy database upgrade procedure.
However this risk IMO is very small because biggest Zabbix customers which are paying for support are using partitioned tables and I know that Zabbix developers are thinking about embedding partitioned critical tables in OOTB database scheme.
Partitioned tables is only known technique allowing to keep performance of interaction with DB backend, so sooner or later it will be IMO fully supported.