-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[connector/routing] Supports matching the statement only once. #28888
Conversation
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.
b2bb725
to
d4780ac
Compare
…hing condition in table
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.
Please remove routingItem.order
field.
done |
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. |
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
The PR hasn't been merged yet. Is there anything else I need to do? |
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? |
Thank you very much for your support. I don't have any other questions. |
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. |
@huange7 I think we're good to go as soon as the conflict is resolved and CI passes |
Thanks. @djaglowski |
…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 <[email protected]>
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: