404 status code returned incorrectly

[david4096]

When using search endpoints a 404 status code is returned if the datasetId is not present. This breaks common conventions, 404 is meant when a resource does not exist. Common search idioms return empty lists when the search terms are not matched on.

[diekhans]

@david4096 this should be a ticket in schemas, as they need to define
exactly what the expected behavior is.

David Steinberg notifications@github.com writes:

When using search endpoints a 404 status code is returned if the datasetId is
not present. This breaks common conventions, 404 is meant when a resource does
not exist. Common search idioms return empty lists when the search terms are
not matched on.

—
Reply to this email directly or view it on GitHub.*

[jeromekelleher]

This is the documented behavior @david4096, and has been discussed a few times. This is a good example: ga4gh/ga4gh-schemas#382

I think Mark's SQL analogy is a good one.

Closing this issue as it is the documented behavior.

[david4096]

Related ga4gh/ga4gh-schemas#382