Using the GraphQL Server on GlycineMine, I found that the pathQuery that gets the data succeeds, but the pathQuery that gets summary info that we use for pagination fails. The queries are identical except the data query asks for a specific page of data whereas the summary query ask for a summary of all the data.
This is the same strategy used for all other queries so I'm not sure why this one would break. I also tried using a different trait for the summaryPath, i.e. &summaryPath=QTL.primaryIdentifier, and got the same result, so I have no idea what the issue might be.
Edit: This appears to be an issue with Trait queries as well:
Using the GraphQL Server on GlycineMine, I found that the pathQuery that gets the data succeeds, but the pathQuery that gets summary info that we use for pagination fails. The queries are identical except the data query asks for a specific page of data whereas the summary query ask for a summary of all the data.
Data query (has
&start=0&size=10
as the end):Summary query (has
&summaryPath=QTL.id
at the end):This is the same strategy used for all other queries so I'm not sure why this one would break. I also tried using a different trait for the summaryPath, i.e.
&summaryPath=QTL.primaryIdentifier
, and got the same result, so I have no idea what the issue might be.Edit: This appears to be an issue with
Trait
queries as well: