Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Breaking change for influxdb receiver #350

Closed
jpkrohling opened this issue Jul 21, 2021 · 1 comment · Fixed by #368
Closed

Breaking change for influxdb receiver #350

jpkrohling opened this issue Jul 21, 2021 · 1 comment · Fixed by #368
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Milestone

Comments

@jpkrohling
Copy link
Member

See open-telemetry/opentelemetry-collector-contrib#4277

We need an upgrade routine for v0.31.0 to handle this change. Basically, if this field exists, it has to be removed. Similar to this:

// Remove deprecated queued_retry processor
if strings.HasPrefix(k.(string), "queued_retry") {
delete(processors, k)
otelcol.Status.Messages = append(otelcol.Status.Messages, fmt.Sprintf("upgrade to v0.19.0 removed the processor %q", k))
continue
}

@jpkrohling jpkrohling added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Jul 21, 2021
@jpkrohling jpkrohling added this to the v0.31.0 milestone Jul 21, 2021
@VineethReddy02 VineethReddy02 self-assigned this Jul 29, 2021
@VineethReddy02
Copy link
Contributor

I would like to work on this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants