-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
feat(analytics): adding kafka dispute analytic events #3549
Conversation
Co-authored-by: Sampras Lopes <lsampras@pm.me>
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.
Add changes in docker_compose.toml
& config.example.toml as well,
Also add the dispute table script in crates/analytics/src/docs
`merchant_connector_id` Nullable(String), | ||
`inserted_at` DateTime DEFAULT now() CODEC(T64, LZ4), | ||
`sign_flag` Int8 | ||
INDEX connectorIndex connector TYPE bloom_filter GRANULARITY 1, |
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.
this would fail since there is no field connector...
Co-authored-by: Sampras Lopes <lsampras@pm.me>
Payment curl:
|
Type of Change
Description
adding dispute events to kafka
Additional Changes
Motivation and Context
How did you test it?
Create a payment curl commented below, I used checkout connector to create dispute
and check on grafana in explore section, select loki and query as
{app="bach"} |= dispute_id
I added SS of local console log in the comment below
Checklist
cargo +nightly fmt --all
cargo clippy