-
Notifications
You must be signed in to change notification settings - Fork 147
test: Add e2e test for on-success-sink #3067
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Vaibhav Tiwari <[email protected]>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3067 +/- ##
=======================================
Coverage 79.64% 79.64%
=======================================
Files 289 289
Lines 65028 65028
=======================================
+ Hits 51791 51794 +3
+ Misses 12687 12684 -3
Partials 550 550 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: Vaibhav Tiwari <[email protected]>
Signed-off-by: Vaibhav Tiwari <[email protected]>
Signed-off-by: Vaibhav Tiwari <[email protected]>
Signed-off-by: Vaibhav Tiwari <[email protected]>
Signed-off-by: Vaibhav Tiwari <[email protected]>
Signed-off-by: Vaibhav Tiwari <[email protected]>
Signed-off-by: Vaibhav Tiwari <[email protected]>
vigith
left a comment
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.
Adding logging fixed it? That sounds suspicious, can you run a couple of times to make sure it is not flaky?
Signed-off-by: Vaibhav Tiwari <[email protected]>
|
Sry, that was just for figuring out what the issue was. The issue was that the redis sink implementation image that I had pushed to quay.io was private. Removed logging and will let the test run again. |
What this PR does / why we need it
As part of completing testing for the on-success sink feature, we want to add an end-2-end test which creates a pipeline with on-success UD sink and validates the messages being written to it.
This PR aims to add this test and the manifest which the test uses to create the said pipeline as well as perform a basic validation based on the testing blueprint for fallback sink.
Related issues
Closes: #3046
Testing
This is the test
Special notes for reviewers
Blocker
Requires release of the next version of any one of the SDKs to successfully work.
Currently built go-sdk image with on-success sink changes, used in the manifest, fails to come up due to version restriction imposed in numaflow-core:
SDK version 0.10.1 must be upgraded to at least 0.10.2, in order to work with the current numaflow versionTo bypass the blocker, we've switched to using the redis sink implementation in Rust with the release of v0.4.0 of the Rust SDK