-
Notifications
You must be signed in to change notification settings - Fork 62
feat: Record READ_ROW metrics for single row calls #1612
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
feat: Record READ_ROW metrics for single row calls #1612
Conversation
src/tabular-api-surface.ts
Outdated
|
||
makeNewRequest(); | ||
return userStream; | ||
return createReadStreamInternal(this, true, opts); |
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.
why is this true? I think createReadStream is for scan not reading a single row?
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.
Yes. This should be false. I did this in a hurry so we should add some tests to check this.
Also pull check into a separate fn
@mutianf Thanks for the reviews. The main purpose of this PR was to provide reviews for one particular change in isolation and get some eyes on it before applying it to all the readRows work. Now that we agree the changes are directionally correct, I think its fine if we merge this into the ReadRows branch and continue review on this code there to unblock progress. |
Description
Mattie pointed out an important requirement here which needs this change in place. This PR ensures the right client side metrics are collected for the right methods.
Impact
User calls with
row.get
will now write client side metrics forREAD_ROW
instead ofREAD_ROWS
as required. This change ensures the right metrics are collected for the right methods.Testing
Additional Information