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

[connector/routing] Supports matching the statement only once. #28888

Merged
merged 10 commits into from
Dec 14, 2023

Conversation

huange7
Copy link
Contributor

@huange7 huange7 commented Nov 4, 2023

Description:

Adding a feature: routing connector supports matching the statement only once

Link to tracking Issue: #26353

Testing:
Basic tests included for the functionality.

Documentation:

Copy link
Member

@songy23 songy23 left a comment

Choose a reason for hiding this comment

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

connector/routingconnector/README.md Outdated Show resolved Hide resolved
connector/routingconnector/README.md Outdated Show resolved Hide resolved
connector/routingconnector/README.md Outdated Show resolved Hide resolved
connector/routingconnector/config.go Outdated Show resolved Hide resolved
connector/routingconnector/config.go Outdated Show resolved Hide resolved
connector/routingconnector/router.go Show resolved Hide resolved
Copy link
Member

@djaglowski djaglowski left a comment

Choose a reason for hiding this comment

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

Please remove routingItem.order field.

@huange7
Copy link
Contributor Author

huange7 commented Nov 28, 2023

Please remove routingItem.order field.

done

connector/routingconnector/README.md Outdated Show resolved Hide resolved
connector/routingconnector/README.md Outdated Show resolved Hide resolved
connector/routingconnector/config.go Show resolved Hide resolved
connector/routingconnector/traces_test.go Show resolved Hide resolved
@djaglowski
Copy link
Member

Related question which can be a separate issue. Is the other (match multiple routes) approach implemented correctly? I am wondering if we are not properly fanning out the data.

For example, if we match routes 1 and 2, we cannot send the same copy of the data to both consumers. We need to use a fanout. In other words, we should build a consumer which contains all the pipelines in both 1 and 2, and send to that.

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 14, 2023
@huange7
Copy link
Contributor Author

huange7 commented Dec 14, 2023

The PR hasn't been merged yet. Is there anything else I need to do?

@djaglowski
Copy link
Member

I've opened a new issue to track my suggestions related to matching multiple routes.

@crobert-1, would you mind reviewing the open conversations and resolving as appropriate.

@huange7, anything else you need from us here other than another review?

@djaglowski djaglowski removed the Stale label Dec 14, 2023
@huange7
Copy link
Contributor Author

huange7 commented Dec 14, 2023

@huange7, anything else you need from us here other than another review?

Thank you very much for your support. I don't have any other questions.

@crobert-1
Copy link
Member

All of my concerns have been addressed, but I don't have permission to resolve the open conversations. This may be because I don't have write access in contrib, but maybe I'm missing something.

@djaglowski
Copy link
Member

@huange7 I think we're good to go as soon as the conflict is resolved and CI passes

@djaglowski djaglowski merged commit b4563f3 into open-telemetry:main Dec 14, 2023
81 of 85 checks passed
@github-actions github-actions bot added this to the next release milestone Dec 14, 2023
@huange7
Copy link
Contributor Author

huange7 commented Dec 15, 2023

@huange7 I think we're good to go as soon as the conflict is resolved and CI passes

Thanks. @djaglowski

cparkins pushed a commit to AmadeusITGroup/opentelemetry-collector-contrib that referenced this pull request Jan 10, 2024
…telemetry#28888)

**Description:** <Describe what has changed.>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
Adding a feature: routing connector supports matching the statement only
once

**Link to tracking Issue:** <Issue number if applicable> open-telemetry#26353

**Testing:** <Describe what testing was performed and which tests were
added.>
Basic tests included for the functionality.

**Documentation:** <Describe the documentation added.>

---------

Co-authored-by: Daniel Jaglowski <jaglows3@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants