-
Notifications
You must be signed in to change notification settings - Fork 805
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 debug logs in PinotTripleVisibilityManager for response comparator testing #5631
Conversation
This method can be moved into chooseVisibilityManagerForRead() so we don't need to do it twice. If it has override, we choose based on the override value, if not, use the original logic. |
The title needs to be updated, we need it for release |
if override := ctx.Value(ContextKey); override == Primary { | ||
manager = v.esVisibilityManager | ||
v.logger.Debug("primary was chosen") |
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.
let's change the message here to make it more reasonable to others, like primary visibility manager elasticsearch was chosen for read
return manager.CountWorkflowExecutions(ctx, request) | ||
} | ||
v.logger.Debug("Pinot Migration log: ContextKey was empty.") | ||
// temporary code: ends here <-- |
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.
probably better to just link to a task ID or a todo
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.
Created a Jira ticket to record this.
What changed?
Added debugging logs to PinotTripleVisibilityManager, for testing pinot response comparator
Why?
Without the logs, we can't know which database Cadence chooses.
How did you test it?
Potential risks
Release notes
Documentation Changes