thor
thor
thor
thor
thor
thor
thor
seph
seph
seph
thor
thor
thor
seph
seph
Stefano Bonicatti
03/12/2024, 6:05 PMStefano Bonicatti
03/12/2024, 6:09 PMStefano Bonicatti
03/12/2024, 6:10 PMStefano Bonicatti
03/12/2024, 6:21 PMStefano Bonicatti
03/12/2024, 6:48 PMseph
thor
thor
thor
thor
thor
thor
tlark
03/19/2024, 8:57 PMnull
values in the JSON output. This matters downstream a lot when data modeling the output from osquery. When I type cast a query result that should be an integer, but the JSON value is a blank string instead of a null
value then I cannot really typecast a nothing to a datatype. So, I have to implement tons of NULLIF
in my data models. This is not a huge deal as I am able to easily work around it, but the labor is definitely increased for every time I want to make the osquery data very useful downstream in our data platform.
So, should I file a gh issue against the main repo? I am still new to osquery and not 100% sure how to report a problem like thisVictor Lyuboslavsky
03/25/2024, 4:11 PMSELECT ROUND(3.531, 2) as num;
returns "distributed_query_433":[{"num":"3.5299999999999998"}]
The correct result can be achieved by using a cast: SELECT CAST(ROUND(3.531, 2) as text) as num;
returns "distributed_query_435":[{"num":"3.53"}]
Should we document this in the Distributed queries section? Something like:
Query results are converted to text strings for transmission, which may result in a loss of precision for numeric values. Result values may be converted to text with SQLite cast,
which may be preferable for some queries. For example: SELECT CAST(ROUND(3.531, 2) as text) as num;
seph