ref(attribute-values): return the most recent items - #8409
Merged
Conversation
MeredithAnya
marked this pull request as ready for review
August 27, 2026 22:19
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 542c4b5. Configure here.
phacops
approved these changes
Aug 27, 2026
This file contains hidden or 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
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.

Related to #8390
We are going to be adding a
last_seento theTraceItemAttributeValuesResponse(among other things) but right now the inner query has no order by.We want to add to order by timestamp so that the 10000 we grab are the most recent, so that when we get the
last_seenakamax(timestamp), this actually represents the most recent data.However in order to get the benefit of
optimize_read_in_orderwe need the ORDER BY be a prefix of the primary key. Since we useproject_ids IN ()syntax, if we just have one project, order by timestamp doesn't optimize the query. So you'd need the full prefix(organization_id, project_id, item_type, timestamp)in the ORDER BY, and with multiple projects that might not make sense since you'd be getting data from one projectexamples
project_id = 1
project_id IN [1]