Skip to content
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

add ContextKey Struct #5606

Merged
merged 6 commits into from
Jan 19, 2024
Merged

add ContextKey Struct #5606

merged 6 commits into from
Jan 19, 2024

Conversation

bowenxia
Copy link
Contributor

What changed?
Added a struct ContextKey

Why?
This is for Pinot/ES response comparator usage:
In mono repo (Cadence-Operation) our workflow needs to query both Pinot and ES in the runtime. So we need to pass in a Context Key-Value (visibility-override = Primary/Secondary) pair to reach this goal. Context key can only be a struct, so we need to create one here in OSS so that both OSS and Mono repo can use it.

How did you test it?
It's just one struct, doesn't include any logics.

Potential risks
none

Release notes

Documentation Changes

@coveralls
Copy link

coveralls commented Jan 19, 2024

Pull Request Test Coverage Report for Build 018d23c8-fdc9-453f-b47e-97c444135c93

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.07%) to 62.6%

Totals Coverage Status
Change from base Build 018d2360-2998-4c74-984a-d4f83b4c5c8c: -0.07%
Covered Lines: 91663
Relevant Lines: 146427

💛 - Coveralls

Copy link
Member

@neil-xie neil-xie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch

@bowenxia bowenxia merged commit a2edc9c into master Jan 19, 2024
16 checks passed
@bowenxia bowenxia deleted the xbowen_add_ContextKey_Struct branch January 19, 2024 23:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants