Error when requesting data

[valentin-bee-transfer]

Describe the bug
I am trying to run the following query, select * from orders, in order to get the corresponding data but it does not work and in the query inspector it says the following:

{
"request": {...},
"response": {
"message": "An error occurred within the plugin",
"messageId": "plugin.downstreamError",
"statusCode": { "statusCode": 500,
"traceID": "56cf6ca5699814f9"
}
}

I'm currently running the same query but with another table and it's working normally. Does anyone know what it could be?

Expected behavior
The expected result would be to be able to fetch the information from the table.

Screenshots

I am using grafana cloud version 9.5.3. From the grafana website.

[pgollangi]

Hi @valentin-bee-transfer thanks for reporting the issue.

It could be problem with the data on the order collection. probably NULL values. there is an open issue with null values.

However is it possible to share more details about this issue? Data, or errors on network or console etc., that would help me better understand the issue.

[compscidr]

We've had a similar issue, and traced it to types. Suppose we have a document with a field that is numeric, and specifically float. Most of the values, but not all have decimals. When we save a value that is even (not a decimal, say 400.0), firestore seems to save it as 400. (you can see other people having issues due to this, for example, here: googleapis/google-cloud-dotnet#3013 (comment)

If we look around here:
https://github.com/pgollangi/firestore-grafana-datasource/blob/main/pkg/plugin/datasource.go#L136

We'll then cast it to an int, and then try to append it to a slice of floats, which has been causing us a similar crash. You may be seeing this if you have any similar patterns in the collection you are querying. It could also be null values as you suggested above.

I think I have an idea for a fix for floats / ints problem. Everything right now is driven on the first value seen. What I was thinking is, if we have a slice of ints, and we encounter a float, we cast the whole slice to a slice of floats. The second half of the solution, is if you encounter an int, and you have a slice of floats, you cast the int to a float before appending to the slice. I'll make a PR with the change, and in the meantime see if I can think of anything for the null problem, so we don't get crashes on nulls.