Use v4 tables for samples and time series

[srikanthccv]

No description provided.

[srikanthccv]

@ankitnayan PTAL

[ankitnayan]

Is the runTimeSeriesReloader loader needed anymore?

[ankitnayan]

Also, we cannot use cumulativetodeltaprocessor for all metrics ingested to our otel-collectors as promql queries won't work with delta right?

[srikanthccv]

Is the runTimeSeriesReloader loader needed anymore?

It caused the OOM earlier. There should be some elaborative way to address that but it's a independent work.

[srikanthccv]

Also, we cannot use cumulativetodeltaprocessor for all metrics ingested to our otel-collectors as promql queries won't work with delta right?

Yes, relying on PromQL is the last thing we want users to do. They are slower and more expensive. It's the worst of both of worlds (neither as good as Prometheus or ClickHouse) to try to remain fully PromQL compatible and ClickHouse. There are two metric types where temporality comes into the picture 1. Histogram 2. Counter and use cases are mostly known with these two, almost every query has some sort of (sum|avg|min|max)(rate|increase) all of which we support in the builder. If there is something we can't support, we will try to make it happen.