Adding immediate caller id to query service. #783
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -138,9 +150,10 @@ message QueryResult { | |||
| // ExecuteRequest is the payload to Execute | |||
| message ExecuteRequest { | |||
| vtrpc.CallerID caller_id = 1; | |||
There was a problem hiding this comment.
I feel it is better to rename this (and following structs) to "effective_caller_id".
There was a problem hiding this comment.
OK I can do that. I was on the fence, now I'm on the other side. :)
|
LGTM with one comment |
alainjobart
added a commit
that referenced
this pull request
Jun 11, 2015
Adding immediate caller id to query service.
rsajwani
pushed a commit
to planetscale/vitess
that referenced
this pull request
Jun 27, 2022
…errors (vitessio#10429) (vitessio#783) * Fail workflow if same error persists too long. Fail for unrecoverable errors also in non-online ddl workflows Signed-off-by: Rohit Nayak <[email protected]> * Update max time default to 15m, was 1m for testing purposes Signed-off-by: Rohit Nayak <[email protected]> * Leverage vterrors for Equals; attempt to address my own nits Signed-off-by: Matt Lord <[email protected]> * sanity: validate range of vreplication_retry_delay and of vreplication_max_time_to_retry_on_error Signed-off-by: Shlomi Noach <[email protected]> * Fix flags test Signed-off-by: Rohit Nayak <[email protected]> * Remove leftover log.Flush() Signed-off-by: Rohit Nayak <[email protected]> * Revert validations min/max settings on retry delay since it is breaking unit tests that set the value to a very small value Signed-off-by: Rohit Nayak <[email protected]> * captilize per request Signed-off-by: Shlomi Noach <[email protected]> Co-authored-by: Matt Lord <[email protected]> Co-authored-by: Shlomi Noach <[email protected]> Signed-off-by: Shlomi Noach <[email protected]> Co-authored-by: Rohit Nayak <[email protected]> Co-authored-by: Matt Lord <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@guoliang100
I think this is correct, let me know if the wording / comment needs work.