Repository navigation
feat(datasetAttributes): provide pagination option + attribute description based evals #1505
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
Merged
nikkikapadia
merged 6 commits into
main
from
nikkikapadia/exp-1291-chooses-field-based-off-of-more-accurate-description
Oct 20, 2026
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
c9fedd8
feat(datasetAttributes): provide pagination option + attribute descri…
nikkikapadia 9279a6d
adjust description evals
nikkikapadia 42ab651
Merge branch 'main' into nikkikapadia/exp-1291-chooses-field-based-of…
nikkikapadia 0b017ea
cursor fixes + fix failing unit test
nikkikapadia f326e74
fix unit test
nikkikapadia f98fbed
Merge branch 'main' into nikkikapadia/exp-1291-chooses-field-based-of…
nikkikapadia File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
[Question] This still means custom attributes are going to take >1 query to get surfaced. Spans have more built-in fields than that (including aggregates).
Should we do something like put custom attributes first and/or put aggregates last? Is there a general sense of which should come first? (genuinely asking, I don't have one myself)
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 they way it works is there are some attributes that are hardcoded because they are the most used and suggested by us. The rest of the attributes come after; more often than not most queries end up using these suggested attributes anyways so it's not really a big deal. Also when we spread the custom attributes on top of the suggested attributes it absorbs all the context and stuff from the attributes endpoint and puts it in the same position (AKA at the top). For attributes that aren't in that first page it will have to query it again.