Open ultrasaurus opened 9 years ago
For launch, we plan to set max page size to be relative low (https://github.com/18F/open-data-maker/issues/191) , which is fine for user experience paging, but not so great for analyzing data.
I believe we should be able to modify the code so the data is a simple pass-thru on the server (rather than exploding everything in memory) so that we could make the following query without using significant memory in the server:
https://ccapi-staging.18f.gov/v1/schools/?school.operating=1&2013.student.size__range=0..&school.region_id=2&school.degrees_awarded.predominant__range=2..3&fields=id,school.name,school.state&per_page=700
I think this got fixed by this: https://github.com/18F/open-data-maker/commit/df7f98b216163eb1f27a038a535817ac95aea742
@ultrasaurus Who should confirm this is done (and then close the issue)?
For launch, we plan to set max page size to be relative low (https://github.com/18F/open-data-maker/issues/191) , which is fine for user experience paging, but not so great for analyzing data.
I believe we should be able to modify the code so the data is a simple pass-thru on the server (rather than exploding everything in memory) so that we could make the following query without using significant memory in the server:
https://ccapi-staging.18f.gov/v1/schools/?school.operating=1&2013.student.size__range=0..&school.region_id=2&school.degrees_awarded.predominant__range=2..3&fields=id,school.name,school.state&per_page=700