Skip to content

chore(events): making events nanosecond level precision #8759

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 4 commits into from
Aug 6, 2025
Merged

chore(events): making events nanosecond level precision #8759

merged 4 commits into from
Aug 6, 2025

Conversation

su-shivanshmathur
Copy link
Contributor

Type of Change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Dependency updates
  • Documentation
  • CI/CD

Description

Nanosecond level precision for time based fields

Additional Changes

  • This PR modifies the API contract
  • This PR modifies the database schema
  • This PR modifies application configuration/environment variables

Motivation and Context

This change would change the timestamp based fields to unix timestamp in nanosecond level precision

How did you test it?

Screenshot 2025-07-25 at 6 31 43 PM

Checklist

  • I formatted the code cargo +nightly fmt --all
  • I addressed lints thrown by cargo clippy
  • I reviewed the submitted code
  • I added unit tests for my changes where possible

@su-shivanshmathur su-shivanshmathur self-assigned this Jul 25, 2025
@su-shivanshmathur su-shivanshmathur requested a review from a team as a code owner July 25, 2025 13:02
@semanticdiff-com SemanticDiff.com
Copy link

semanticdiff-com bot commented Jul 25, 2025 •
edited
Loading

Review changes with  SemanticDiff

Changed Files
File Status
  crates/router/src/services/kafka/dispute_event.rs  12% smaller
  crates/router/src/services/kafka/refund_event.rs  7% smaller
  crates/router/src/services/kafka/fraud_check_event.rs  6% smaller
  crates/router/src/services/kafka/payment_attempt_event.rs  0% smaller
  crates/router/src/services/kafka/payment_intent_event.rs  0% smaller

@su-shivanshmathur su-shivanshmathur linked an issue Jul 25, 2025 that may be closed by this pull request
[FEATURE] Add v2 kafka events for payment_intent, payment_attempt and refund #8379
Closed
hrithikesh026
hrithikesh026 reviewed Jul 25, 2025
View reviewed changes
@Gnanasundari24 Gnanasundari24 added this pull request to the merge queue Aug 6, 2025
Merged via the queue into main with commit c6fcf29 Aug 6, 2025
15 of 20 checks passed
@Gnanasundari24 Gnanasundari24 deleted the kafka_events_v2_changes branch August 6, 2025 12:20
pixincreate added a commit that referenced this pull request Aug 7, 2025
@pixincreate
Merge branch 'main' of github.com:juspay/hyperswitch into connector/n…
23b20dc 
…ordea-sepa

* 'main' of github.com:juspay/hyperswitch:
  fix(router): [worldpayvantiv] dispute validations and statuses (#8862)
  chore(version): 2025.08.07.0
  feat(connector): [WORLDPAYVANTIV] Populate Network Decline Error Code & Message (#8856)
  feat(router): add support for partial authorization (#8833)
  feat(gRPC): build gRPC client interface to initiate communication with recovery-decider service (#8178)
  fix(connector): [CYBERSOURCE] fix response field for netcetera authentication response (#8850)
  chore(events): making events nanosecond level precision (#8759)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@hrithikesh026 hrithikesh026 hrithikesh026 left review comments

@SanchithHegde SanchithHegde SanchithHegde approved these changes

@sai-harsha-vardhan sai-harsha-vardhan sai-harsha-vardhan approved these changes

@ShankarSinghC ShankarSinghC ShankarSinghC approved these changes

Assignees

@su-shivanshmathur su-shivanshmathur

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[FEATURE] Add v2 kafka events for payment_intent, payment_attempt and refund
6 participants
@su-shivanshmathur @SanchithHegde @sai-harsha-vardhan @hrithikesh026 @ShankarSinghC @Gnanasundari24