3. For some of the tables, I can’t even figure out where the data would be coming from — for instance,

durationSort

isn’t a materialized view … but also doesn’t seem to have any writes I could find while spelunking the SigNoz codebase … how do these get populated? ditto

top_level_operations

, where from?

durationSort

is a projection https://github.com/SigNoz/signoz-otel-collector/blob/main/exporter/clickhousetracesexporter/feature_manager.go#L58. You can disable this feature https://github.com/SigNoz/signoz-otel-collector/blob/main/exporter/clickhousetracesexporter/feature_manager.go#L12

Hm, I saw

feature_manager.go

in my grepping, but it didn’t look like it was doing any writing — just creating the table; and I didn’t see any Clickhouse arguments that made it obvious how it’s receiving data. I see the

enableTimestampSortFeature

that adds a

PROJECTION

, but none for

durationSort

? I may just be dense! (this isn’t pressing, just curious)

durationSort MV is here https://github.com/SigNoz/signoz-otel-collector/blob/main/exporter/clickhousetracesexporter/migrations/000011_init_durationMV.up.sql