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

enhancement: make synchronous transforms take a mutable receiver #480

Merged
merged 1 commit into from
Feb 6, 2025

Conversation

tobz
Copy link
Member

@tobz tobz commented Feb 6, 2025

Summary

This PR switches SynchronousTransform::transform_buffer from taking &self to taking &mut self.

This unlocks the ability for synchronous transforms to actually maintain mutable state that is needed for transforming metrics. It was an oversight on my part when originally designing SynchronousTransform to not do so, so we're just rectifying things here.

Change Type

  • Bug fix
  • New feature
  • Non-functional (chore, refactoring, docs)
  • Performance

How did you test this PR?

N/A

References

N/A

@tobz tobz requested a review from a team as a code owner February 6, 2025 20:23
@tobz tobz added the type/enhancement An enhancement in functionality or support. label Feb 6, 2025
@github-actions github-actions bot added area/core Core functionality, event model, etc. area/components Sources, transforms, and destinations. transform/chained Chained transform. transform/host-enrichment Host Enrichment synchronous transform. labels Feb 6, 2025
@tobz tobz merged commit b8af303 into main Feb 6, 2025
17 of 18 checks passed
@tobz tobz deleted the tobz/synchronous-transform-mutable-receiver branch February 6, 2025 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/components Sources, transforms, and destinations. area/core Core functionality, event model, etc. transform/chained Chained transform. transform/host-enrichment Host Enrichment synchronous transform. type/enhancement An enhancement in functionality or support.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants