Null field queries are converted into generic string queries

[youeyoue]

• Sometimes a node won't have the report-timestamp field set yet (same can be applied to other fields).

I haven't been able to figure out how to directly search for a field that is null.

If I do the following search:

#node.report-timestamp = null

The following query is ran:

/v4/nodes?include-total=true&limit=50&offset=0&order-by=%5B%7B%22field%22:%22certname%22,%22order%22:%22asc%22%7D%5D&query=%5B%22in%22,%22certname%22,%5B%22extract%22,%22certname%22,%5B%22select-nodes%22,%5B%22%3D%22,%22report-timestamp%22,%22null%22%5D%5D%5D%5D

This has "null" wrapped in quotes: %22null%22

However, if you remove the quotes and manually execute the query, you will get a JSON object with results as expected.

/v4/nodes?include-total=true&limit=50&offset=0&order-by=%5B%7B%22field%22:%22certname%22,%22order%22:%22asc%22%7D%5D&query=%5B%22in%22,%22certname%22,%5B%22extract%22,%22certname%22,%5B%22select-nodes%22,%5B%22%3D%22,%22report-timestamp%22,null%5D%5D%5D%5D

This seems to indicate that null fields aren't supported. Or that it's not obvious.