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
Use estimated dataset count for index page query #4114
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #4114 +/- ##
========================================
Coverage 28.84% 28.85%
========================================
Files 768 769 +1
Lines 97035 97127 +92
Branches 1120 1128 +8
========================================
+ Hits 27991 28026 +35
- Misses 69044 69101 +57
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
allDatasets: datasets(search: "") { | ||
total | ||
} | ||
allDatasets: estimatedDatasetCount |
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.
do we also need to update line 29 of this file? Or will it work as is?
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.
The name of the field is still aliased as allDatasets
, I think it should work
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.
My mistake, total
is missing 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.
Tested locally with empty pages. LGTM!
What changes are proposed in this pull request?
Replaces the
datasets(search: "")
field query for the index page with an optimized estimated dataset count. The current approach is potentially very slow for a database with a large number of datasets.How is this patch tested? If it is not, please explain why.
e2e coverage
Release Notes
What areas of FiftyOne does this PR affect?
fiftyone
Python library changes