Closed florianl closed 3 months ago
Changing this type does not break compatibility with the original pprof, as the original pprof does not have this element in
message Location
.
Does it still meet the requirement of "every valid pprof profile is also a valid Otel profile"?
Does it still meet the requirement of "every valid pprof profile is also a valid Otel profile"?
@tigrannajaryan - yes it does. As type_index
was introduced by the OTel Profiling SIG it does not affect original pprof profiles. In general original pprof profiles use int64
as index type and this PR aligns the OTel Profiling SIG introduced element to also use int64
as its type.
Love this change! – are there any blockers to iron out before it can be merged?
friendly ping @open-telemetry/specs-approvers - can this change get merged?
@felixge , @petethepig and @christos68k from the @open-telemetry/profiling-maintainers group approved this change already.
With
Mapping.filename
,Function.name
,Label.key
and others, the type of the index into the string table is alwaysint64
. For consistency align the type ofLocation.type_index
, which is also an index into the string table, toint64
.type_index
is an element introduced by the OTel Profiling SIG and was added tomessage Location
. Changing this type does not break compatibility with the original pprof, as the original pprof does not have this element inmessage Location
.FYI: @petethepig @open-telemetry/profiling-maintainers