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.

Sign up for GitHub

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

Jump to bottom

[pdata] Implement Go 1.23 style iterators #11982

Open
yurishkuro opened this issue Dec 25, 2024 · 4 comments · May be fixed by #12380
Open

[pdata] Implement Go 1.23 style iterators #11982

yurishkuro opened this issue Dec 25, 2024 · 4 comments · May be fixed by #12380
Assignees
@mauri870

Comments

@yurishkuro
Copy link
Member

yurishkuro commented Dec 25, 2024 •
edited
Loading

Is your feature request related to a problem? Please describe.

Iterating through pdata structures today is pretty convoluted, e.g.

for i := 0; i < traces.ResourceSpans().Len(); i++ {
	resource := traces.ResourceSpans().At(i)
	for j := 0; j < resource.ScopeSpans().Len(); j++ {
		scope := resource.ScopeSpans().At(j)
		for k := 0; k < scope.Spans().Len(); k++ {
			span := scope.Spans().At(k)

Describe the solution you'd like
Go 1.23 introduced the ability to use iterators for looping through custom structs. The above code could look like this, if we introduce iterator functions to pdata, e.g. Seq() and Seq2():

for resource := range traces.ResourceSpans().Seq() {
	for scope := range resource.ScopeSpans().Seq() {
		for span := range scope.Spans().Seq() {
for i, resource := range traces.ResourceSpans().Seq2() {
	for j, scope := range resource.ScopeSpans().Seq2() {
		for k, span := range scope.Spans().Seq2() {
@bogdandrutu
Copy link
Member

@yurishkuro good call, will do when we move to minimum supported version to be 1.23

@mauri870
Copy link
Contributor

mauri870 commented Jan 2, 2025 •
edited
Loading

I think this is a perfect use case for iterators, the way this is implemented today is quite verbose to write and almost every single use case requires looping over the entries in some way.

I suggest we go with an All method, following the api signature for the already existing maps and slices counterparts.

Since this involves changes in autogenerated code, there might be oportunities for reusing existing iterator routines from the standard library, for example ResourceSpans uses an slice internally.

@mauri870
Copy link
Contributor

I started working on this main...mauri870:opentelemetry-collector:pdata-iterator-all. It requires Go 1.23 so we cannot accept it until all the other collector packages are bumped to 1.23.

@mauri870 mauri870 mentioned this issue Feb 12, 2025
Closed
@mauri870
Copy link
Contributor

Now that the ecosystem moved to Go 1.23 I will resume working on this. I should have a PR up this week.

@mauri870 mauri870 linked a pull request Feb 13, 2025 that will close this issue
Open
@djaglowski djaglowski mentioned this issue Feb 13, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mauri870 mauri870

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

pdata: add iterator All method to slice and map types mauri870/opentelemetry-collector
3 participants
@bogdandrutu @yurishkuro @mauri870