-
Notifications
You must be signed in to change notification settings - Fork 528
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
Remove package transform #5729
Merged
Merged
Remove package transform #5729
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is no longer needed. Transformation to beat.Events longer requires parameterisation, with all customisable transformations moving to model processing.
Transformation should now be more or less instant, and errors cannot occur, so it is no longer useful to trace these operations.
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errors
Expand to view the tests failures
|
simitt
approved these changes
Jul 16, 2021
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
mergify bot
pushed a commit
that referenced
this pull request
Jul 16, 2021
* Remove package transform This is no longer needed. Transformation to beat.Events longer requires parameterisation, with all customisable transformations moving to model processing. * publish: don't create spans for transformation Transformation should now be more or less instant, and errors cannot occur, so it is no longer useful to trace these operations. (cherry picked from commit e63fd60)
axw
added a commit
that referenced
this pull request
Jul 16, 2021
* Remove package transform This is no longer needed. Transformation to beat.Events longer requires parameterisation, with all customisable transformations moving to model processing. * publish: don't create spans for transformation Transformation should now be more or less instant, and errors cannot occur, so it is no longer useful to trace these operations. (cherry picked from commit e63fd60) Co-authored-by: Andrew Wilkins <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation/summary
Remove package transform, which is no longer needed. Transformation to beat.Events longer requires parameterisation, with all customisable transformations moving to model processing. We could probably also remove the context parameter to the transformable interface, but I've left it there for now as it's not actively causing problems.
Transformation should now be more or less instant, and errors cannot occur, so it is no longer useful to instrument these operations.
Checklist
- [ ] Update CHANGELOG.asciidoc- [ ] Documentation has been updatedHow to test these changes
The only user-visible change is that spans are no longer produced for event transformation. This can be observed by enabling instrumentation (
-E instrumentation.enabled=true
), sending some events to the server, and then checking that no "Transform" spans are produced.Related issues
#3565