|
| 1 | +# Use this changelog template to create an entry for release notes. |
| 2 | + |
| 3 | +# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' |
| 4 | +change_type: breaking |
| 5 | + |
| 6 | +# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver) |
| 7 | +component: clickhouseexporter |
| 8 | + |
| 9 | +# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). |
| 10 | +note: Upgrade trace SpanKind and StatusCode string values |
| 11 | + |
| 12 | +# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. |
| 13 | +issues: [34799] |
| 14 | + |
| 15 | +# (Optional) One or more lines of additional information to render under the primary note. |
| 16 | +# These lines will be padded with 2 spaces and then inserted directly into the document. |
| 17 | +# Use pipe (|) for multiline entries. |
| 18 | +subtext: | |
| 19 | + This change updates the output of the trace SpanKind and StatusCode fields to be consistent |
| 20 | + with the specification's enum values. While this change will not break any deployments, it may affect |
| 21 | + queries dependent on the old enum names. |
| 22 | + |
| 23 | + For more details on old->new values, see this related PR: |
| 24 | + https://github.com/open-telemetry/opentelemetry-collector/pull/6250 |
| 25 | +
|
| 26 | +
|
| 27 | +# If your change doesn't affect end users or the exported elements of any package, |
| 28 | +# you should instead start your pull request title with [chore] or use the "Skip Changelog" label. |
| 29 | +# Optional: The change log or logs in which this entry should be included. |
| 30 | +# e.g. '[user]' or '[user, api]' |
| 31 | +# Include 'user' if the change is relevant to end users. |
| 32 | +# Include 'api' if there is a change to a library API. |
| 33 | +# Default: '[user]' |
| 34 | +change_logs: [] |
0 commit comments