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
Introducing pipedstat model #2261
Conversation
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.
Code coverage for golang is
|
Code coverage for golang is
|
typo in the PR title
|
|
||
import "validate/validate.proto"; | ||
|
||
message PipedStat { |
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.
How about adding PipedID into this message?
I know we are having that ID from the map key but ID inside its data could be helpful as well.
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.
Sure 👍 Btw I'm thinking about the current model name, just want to make it PipedMetrics. In that case, PipedMetrics.PipedID and PipedMetrics.Stat looks better than PipedStat.PipedID and PipedStat.Stat as currently. Just wonder is that name too generics or something 🤔 How do you think about that?
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.
I think PipedMetrics
is good too. But currently, our RPC name is Report...Stats
, right?
So maybe we should keep that model name as PipedStat
and change its Stat
field to Metrics
.
Or we can reuse the old PipedStats
model, deprecate unused fields and add new fields like PipedID
, Metrics
.
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.
So maybe we should keep that model name as PipedStat and change its Stat field to Metrics.
Get your point, lets me adopt this 👍 ( Personally don't think the name should be XXXStats
since this message covers only a single value of piped committed stat at a time )
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.
Addressed by ae07feb 🙏
The following ISSUES will be created once got merged. If you want me to skip creating the issue, you can use Details1. Filter returning piped metrics by value timestamp.This was created by todo plugin since "TODO:" was found in ae07feb when #2261 was merged. cc: @khanhtc1202. |
/todo skip |
Cool |
/approve |
Code coverage for golang is
|
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?: