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

[schema processor] Part 3 - Modifiers and Revisions #12147 #17020

Merged

Conversation

MovieStoreGuy
Copy link
Contributor

This is a new PR of #12147

No existing changes have happened.

cc: @tigrannajaryan

@runforesight
Copy link

runforesight bot commented Dec 14, 2022

Foresight Summary

    
Major Impacts

build-and-test-windows duration(5 seconds) has decreased 41 minutes 44 seconds compared to main branch avg(41 minutes 49 seconds).
View More Details

✅  tracegen workflow has finished in 58 seconds (1 minute 30 seconds less than main branch avg.) and finished at 25th Jan, 2023.


Job Failed Steps Tests
build-dev -     🔗  N/A See Details
publish-latest -     🔗  N/A See Details
publish-stable -     🔗  N/A See Details

⭕  changelog workflow has finished in 5 seconds (2 minutes 41 seconds less than main branch avg.) and finished at 24th Feb, 2023.


Job Failed Steps Tests
changelog -     🔗  N/A See Details

⭕  build-and-test-windows workflow has finished in 5 seconds (41 minutes 47 seconds less than main branch avg.) and finished at 24th Feb, 2023.


Job Failed Steps Tests
windows-unittest-matrix -     🔗  N/A See Details
windows-unittest -     🔗  N/A See Details

✅  check-links workflow has finished in 43 seconds (1 minute 41 seconds less than main branch avg.) and finished at 24th Feb, 2023.


Job Failed Steps Tests
changed files -     🔗  N/A See Details
check-links -     🔗  N/A See Details

✅  telemetrygen workflow has finished in 59 seconds (2 minutes 1 second less than main branch avg.) and finished at 24th Feb, 2023.


Job Failed Steps Tests
build-dev -     🔗  N/A See Details
publish-latest -     🔗  N/A See Details
publish-stable -     🔗  N/A See Details

✅  prometheus-compliance-tests workflow has finished in 11 minutes 7 seconds (⚠️ 1 minute 57 seconds more than main branch avg.) and finished at 24th Feb, 2023.


Job Failed Steps Tests
prometheus-compliance-tests -     🔗  ✅ 21  ❌ 0  ⏭ 0    🔗 See Details

✅  build-and-test workflow has finished in 53 minutes 28 seconds (15 minutes 15 seconds less than main branch avg.) and finished at 24th Feb, 2023.


Job Failed Steps Tests
correctness-metrics -     🔗  ✅ 2  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.19, internal) -     🔗  ✅ 561  ❌ 0  ⏭ 0    🔗 See Details
correctness-traces -     🔗  ✅ 17  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.20, internal) -     🔗  ✅ 561  ❌ 0  ⏭ 0    🔗 See Details
unittest-matrix (1.19, extension) -     🔗  ✅ 537  ❌ 0  ⏭ 0    🔗 See Details
setup-environment -     🔗  N/A See Details
check-codeowners -     🔗  N/A See Details
check-collector-module-version -     🔗  N/A See Details
lint-matrix (receiver-0) -     🔗  N/A See Details
lint-matrix (receiver-1) -     🔗  N/A See Details
lint-matrix (processor) -     🔗  N/A See Details
lint-matrix (exporter) -     🔗  N/A See Details
lint-matrix (extension) -     🔗  N/A See Details
lint-matrix (internal) -     🔗  N/A See Details
lint-matrix (other) -     🔗  N/A See Details
build-examples -     🔗  N/A See Details
checks -     🔗  N/A See Details
integration-tests -     🔗  N/A See Details
unittest-matrix (1.20, receiver-0) -     🔗  N/A See Details
unittest-matrix (1.20, receiver-1) -     🔗  N/A See Details
unittest-matrix (1.20, processor) -     🔗  N/A See Details
unittest-matrix (1.20, exporter) -     🔗  N/A See Details
unittest-matrix (1.20, extension) -     🔗  N/A See Details
unittest-matrix (1.20, other) -     🔗  N/A See Details
unittest-matrix (1.19, receiver-0) -     🔗  N/A See Details
unittest-matrix (1.19, receiver-1) -     🔗  N/A See Details
unittest-matrix (1.19, processor) -     🔗  N/A See Details
unittest-matrix (1.19, exporter) -     🔗  N/A See Details
unittest-matrix (1.19, other) -     🔗  N/A See Details
lint -     🔗  N/A See Details
unittest (1.20) -     🔗  N/A See Details
unittest (1.19) -     🔗  N/A See Details
cross-compile (darwin, amd64) -     🔗  N/A See Details
cross-compile (darwin, arm64) -     🔗  N/A See Details
cross-compile (linux, 386) -     🔗  N/A See Details
cross-compile (linux, amd64) -     🔗  N/A See Details
cross-compile (linux, arm64) -     🔗  N/A See Details
cross-compile (linux, arm) -     🔗  N/A See Details
cross-compile (linux, ppc64le) -     🔗  N/A See Details
cross-compile (windows, 386) -     🔗  N/A See Details
cross-compile (windows, amd64) -     🔗  N/A See Details
build-package (deb) -     🔗  N/A See Details
build-package (rpm) -     🔗  N/A See Details
windows-msi -     🔗  N/A See Details
publish-check -     🔗  N/A See Details
publish-stable -     🔗  N/A See Details
publish-dev -     🔗  N/A See Details

✅  e2e-tests workflow has finished in 17 minutes 51 seconds and finished at 24th Feb, 2023.


Job Failed Steps Tests
kubernetes-test (v1.26.0) -     🔗  N/A See Details
kubernetes-test (v1.25.3) -     🔗  N/A See Details
kubernetes-test (v1.24.7) -     🔗  N/A See Details
kubernetes-test (v1.23.13) -     🔗  N/A See Details

✅  load-tests workflow has finished in 28 minutes 41 seconds (⚠️ 11 minutes 29 seconds more than main branch avg.) and finished at 24th Feb, 2023.


Job Failed Steps Tests
setup-environment -     🔗  N/A See Details
loadtest (TestIdleMode) -     🔗  N/A See Details
loadtest (TestBallastMemory|TestLog10kDPS) -     🔗  N/A See Details
loadtest (TestMetric10kDPS|TestMetricsFromFile) -     🔗  N/A See Details
loadtest (TestMetricResourceProcessor|TestTrace10kSPS) -     🔗  N/A See Details
loadtest (TestTraceNoBackend10kSPS|TestTrace1kSPSWithAttrs) -     🔗  N/A See Details
loadtest (TestTraceBallast1kSPSWithAttrs|TestTraceBallast1kSPSAddAttrs) -     🔗  N/A See Details
loadtest (TestTraceAttributesProcessor) -     🔗  N/A See Details

🔎 See details on Foresight

*You can configure Foresight comments in your organization settings page.

@MovieStoreGuy MovieStoreGuy added the Skip Changelog PRs that do not require a CHANGELOG.md entry label Dec 14, 2022
@github-actions
Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@github-actions github-actions bot added the Stale label Dec 28, 2022
@tigrannajaryan
Copy link
Member

@MovieStoreGuy I reviewed #12147 earlier. Does this need another round of review?

@MovieStoreGuy
Copy link
Contributor Author

@MovieStoreGuy I reviewed #12147 earlier. Does this need another round of review?

This is the same PR but nether of us could reopen the stale PR.

@github-actions
Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@MovieStoreGuy
Copy link
Contributor Author

I believe I had addressed all the comments left by @tigrannajaryan in the last reviewed pinned.

I know in my delay that schema parser as adopted v1.1, however, I would like to get this out first that works with v1.0 so the semantic convetions can be defined as stable and v1.1 can be added in once this component is added to the release.

@MovieStoreGuy MovieStoreGuy force-pushed the msg/part-3-schema-revisions branch 3 times, most recently from a82ea85 to f4911e7 Compare January 25, 2023 04:12
Copy link
Member

@bogdandrutu bogdandrutu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will think more to suggest some better design/names.

Copy link
Member

@tigrannajaryan tigrannajaryan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on this @MovieStoreGuy !

@tigrannajaryan
Copy link
Member

@MovieStoreGuy is this still in progress? Do you need an additional review?

@MovieStoreGuy
Copy link
Contributor Author

Still in progress, I just have been unfortunate with trying to find time to resolve this.

Talking with @mx-psi is keen to help see the implementation finished and take over my current work.

@mx-psi
Copy link
Member

mx-psi commented Apr 19, 2023

Will discuss further with @MovieStoreGuy and have a look at this next week to see how to continue.

@MovieStoreGuy if you have the time, would you mind going through the conversations and marking as resolved any that no longer need addressing?

@tigrannajaryan
Copy link
Member

@MovieStoreGuy sounds good. Let me know if you need any help from me. I think it is important that we complete this. The lack of the transform processor comes up in our discussions on how to better handle semantic convention changes.

if matched {
k, updated[key] = key, struct{}{}
} else {
// TODO: Since the spec hasn't decided the behavior on what
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Link to an issue for deciding this in the comment?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not yet, was raised by @tigrannajaryan in a comment so I will raise it in the morning on the spec repo (or if anyone else gets to it before me).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to make a decision on open-telemetry/opentelemetry-specification#3497
Depending on the outcome the performance may be significantly impacted.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this must be solved before marking the component as alpha and adding it to our official builds, but still I don't think it should block merging this PR in the interest of moving forward with other parts of the implementation

processor/schemaprocessor/internal/migrate/doc.go Outdated Show resolved Hide resolved
@MovieStoreGuy
Copy link
Contributor Author

Hey @tigrannajaryan , @mx-psi ,

Are we okay to merge this PR? I wouldn't mind getting this in so I can work on the final PR for this to get an in development module out.

Copy link
Member

@tigrannajaryan tigrannajaryan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

}

func newAttributeChangeSetSliceFromChanges(attrs ast.Attributes) *migrate.AttributeChangeSetSlice {
values := make([]*migrate.AttributeChangeSet, 0, 10)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: since it has no particular importance I think it can be safely deleted, values := make([]*migrate.AttributeChangeSet) should be good enough.

@MovieStoreGuy MovieStoreGuy added the ready to merge Code review completed; ready to merge by maintainers label May 17, 2023
@MovieStoreGuy
Copy link
Contributor Author

Sorry, just removing some of the generics usage since I can use ast.AttributeMap where map[AttributeKey]AttributeKey was being defined without issue.

@mx-psi
Copy link
Member

mx-psi commented May 17, 2023

Let's wait until EOW to give @bogdandrutu time to review and I will merge if no new concerns are raised :)

A modifier allows mutating a signal from a previous version to the
current one and vice versa.
[schema processor] Adding revisions

A revision handles applying the modifiers to incoming signals and
converting a signal to the next version.
Following patterns similar to databases where you'd apply changes
and rollback. the Migrate packages follows these designs to help make it
clear what it is trying to do.
@mx-psi
Copy link
Member

mx-psi commented May 23, 2023

@bogdandrutu I am going to merge this, we won't move this out of 'In Development' until we clarify #17020 (comment) but since we have an issue tracking this on the spec this is ready to merge. Please open follow up issues if you have any comments

@mx-psi mx-psi merged commit 085abb9 into open-telemetry:main May 23, 2023
85 checks passed
@github-actions github-actions bot added this to the next release milestone May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
processor/schema Schema processor ready to merge Code review completed; ready to merge by maintainers Skip Changelog PRs that do not require a CHANGELOG.md entry
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants