Open Seanspt opened 3 years ago
The link you provided does not work.
There is a relevant example in the spec as "batch receiving": https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/messaging.md#batch-receiving I don't think this has been tested in practice though.
The link you provided does not work.
There is a relevant example in the spec as "batch receiving": https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/messaging.md#batch-receiving I don't think this has been tested in practice though.
Thanks, the aggregation operation seems more related to Batch processing. As descibed here, links should be used is aggregation/batch processing.
In spark streaming/flink applications, multiple messages could be aggregated and producing a single message.
The structure suggested in semantic_conventions seems not able to handle the aggregation scenario.
Should mutiple parent be supported for that?