How can I add partitions to the auto generated physical table for metrics and traces coming in from OTEL (and the logical tables if needed)? I am shipping in my PoC 5% or our total data so far and I have 1 datanode using 29Gi out of 32Gi on the pod limit. I ran into the same issue to the point that I crashed the datanode going OOM due to log volume and broke it down across 16 partitions. I would like to do the same to protect the datanodes but can't figure out how. When I did an alter table and added partitions on the

greptime_physical_table

all querying of data from the logical tables returned errors about invalid regions.

After adding the partition, did you see any new regions when you ran

SHOW CREATE TABLE {your_table}

?

@Weny Xu So it took some work and some digging through docs to find a single line that states if you want to use the generated metrics engine with partitioning that you have to pre-create the table with a set of low cardinality fields and then partition on those. But the docs are not very clear that you can't use a field that is of INT type as a primary key on a metrics table, so had to move my shard key to a STRING and pad the values from the OTel collector.