-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix: message properties should contain reqType instead of messageID [PIPE-1557] #35
base: main
Are you sure you want to change the base?
Conversation
14b7885
to
c5471f0
Compare
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.
Does the GW already infers the messageID
if it's not there? I'm talking about the internal batch endpoint that the src-router hits.
I'm asking to make sure we can release these changes in a backwards compatible manner.
I'm assuming that at the moment the GW expects a messageID and does not expect a request type in the properties. If that's the case then we would need a release of rudder-server first that infers the messageID (unless it already does) and it checks for request type in both the properties and the body. This way we can rollback the HA ingestion services without having to rollback the GW. Once all is released (and stable) we can then drop the extra checks in the GW. Wdyt?
Gateway simply sets the request type to
And messageID is used to fill the parameters, which isn't even used in processor tbh, it's fetched from the payload. so imo it's fine if it's not populated. For the request type, we'd have to release server - but only for the purpose of stats, the pipeline can go on. |
@Sidddddarth OK cool so it sounds like we need a few GW changes first. Not just for stats though. |
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.
LGTM, but let's not merge until we have a proper release of rudder-server that is compatible with both versions.
Description
message properties should contain reqType instead of messageID since ingestion will no longer have messageID and gw infers it. Also, reqType should be passed to gw.
Linear Ticket
https://linear.app/rudderstack/issue/PIPE-1557/payload-should-not-be-modified-in-ingestionsvc
Security