Error when `limit>500` about monarchr HOT 3 CLOSED

Closing, these are addressed in the new 1.0 release; fetch_nodes() now handles fetching by query ID and by bulk node properties, whereas monarch_search() uses the monarch search API, and properly handles limit > 500 case.

from monarchr.

This appears to be caused by the Monarch API's search endpoint, which returns a 500 when the limit > 500 (tried over at https://api-v3.monarchinitiative.org/v3/docs#/search/search_v3_api_search_get).

I'm not sure if it's feasible to get that bumped but we should at least handle it gracefully in the package :)

Regarding bulk "grab all nodes of category X" kinds of queries, that seems like something we can better handle with the graph engine/neo4j than the keyword search (I've also not tried NULL for the query on that one, hadn't thought of that use case!)

from monarchr.

This appears to be caused by the Monarch API's search endpoint, which returns a 500 when the limit > 500 (tried over at https://api-v3.monarchinitiative.org/v3/docs#/search/search_v3_api_search_get).

I'm not sure if it's feasible to get that bumped but we should at least handle it gracefully in the package :)

Makes sense, I figured it was something like that.

Regarding bulk "grab all nodes of category X" kinds of queries, that seems like something we can better handle with the graph engine/neo4j than the keyword search (I've also not tried NULL for the query on that one, hadn't thought of that use case!)

Totally agree, using the KG for bulk queries would be super helpful here.

from monarchr.