What type of enhancement is this?
API improvement, Configuration
What does the enhancement do?
auto_create_table` currently always creates mito-engine tables. There is no way to have it create metric-engine logical tables instead.
For workloads with many dynamically-appearing metrics (IIoT, multi-tenant observability), the metric engine's shared physical table is the right storage model, but today you must pre-create every table via SQL with ENGINE = metric before data arrives.
Proposal: Add a hint or config option so that when auto_create_table fires, it creates a logical table on the specified physical table instead of a standalone mito table. If the physical table doesn't exist yet, create it automatically.
Implementation challenges
No response
What type of enhancement is this?
API improvement, Configuration
What does the enhancement do?
auto_create_table` currently always creates mito-engine tables. There is no way to have it create metric-engine logical tables instead.
For workloads with many dynamically-appearing metrics (IIoT, multi-tenant observability), the metric engine's shared physical table is the right storage model, but today you must pre-create every table via SQL with
ENGINE = metricbefore data arrives.Proposal: Add a hint or config option so that when
auto_create_tablefires, it creates a logical table on the specified physical table instead of a standalone mito table. If the physical table doesn't exist yet, create it automatically.Implementation challenges
No response