The problem here is that we have components like batchprocessor or
others which are keeping a reference of the data and eventually
modifying them without any concurrent access protection. Hence, it is
required for the callers to not access any data that were passed
downstream.
This is not a backwards incompatible change, since pdata is not
thread-safe this is a MUST to have here (consider a bug for not being
documented) otherwise things will not work in the processing pipelines.
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
This adds profiles support for consumers.
<!-- Issue number if applicable -->
#### Link to tracking issue
Based on the discussion in #10375.
---------
Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com>
* [chore] use license shortform
To remain consistent w/ contrib repo, see https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/22052
Signed-off-by: Alex Boten <aboten@lightstep.com>
* make goporto
Signed-off-by: Alex Boten <aboten@lightstep.com>
---------
Signed-off-by: Alex Boten <aboten@lightstep.com>
Split all `pdata` related code by type and move it from `model` to the new module `pdata`.
- `model/pdata` and `model/otlp` are moved to `pdata/plog`, `pdata/pmetric` and `pdata/ptrace`.
- `model/otlpgrpc` is moved to `pdata/plogotlp`, `pdata/pmetricotlp` and `pdata/ptraceotlp`.
Now all the API in `model` except for `model/semconv` is deprecated.