-
Notifications
You must be signed in to change notification settings - Fork 23
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: add support for ordering in QueryRecords #340
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.
added a few comments. let me know what you think.
api/open_saves.proto
Outdated
} | ||
|
||
// Property name to order by. | ||
string property_name = 1; |
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.
not a request but will we allow sorting by system properties (like updated_at or blob_size)? In that case using oneof might make sense here (although we only have property_name right now).
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.
@loranger2k @labheshd what do you think? Is there a request to sort by these fields?
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.
lgtm
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.
lgtm with comments
What type of PR is this?
/kind feat
What this PR does / Why we need it:
Adds the ability to query records and return them in a sorted order, given that the proper composite index is created.
Which issue(s) this PR fixes:
Closes #337
Special notes for your reviewer: