fails for rows on which we apply the to_string function. We also need to make sure that there are no other schemas that might throw errors because of this.
fails for rows on which we apply the to_string function. We also need to make sure that there are no other schemas that might throw errors because of this.
There is a disable unit test with this particular issue. It has to be enabled once this is fixed.
fails for rows on which we apply the to_string function. We also need to make sure that there are no other schemas that might throw errors because of this.
This can be reproduced with this query:
There is a disable disabled unit test with this particular issue ticket id. It has to be enabled once this is fixed.
fails for rows on which we apply the to_string function. We also need to make sure that there are no other schemas that might throw errors because of this.
This can be reproduced with this query:
{code:java} ["extract", [["function", "to_string", "value"]], ["=","name", "uptime_seconds"]] {code} on the facts endpoint.
*There is a disabled unit test with this ticket id. It has to be enabled once this is fixed.*
fails for rows on which we apply the to_string function. We also need to make sure that there are no other schemas that might throw errors because of this.
This can be reproduced with this query:
{code:java} ["extract", [["function", "to_string", "value"]], ["=","name", "uptime_seconds"]] {code} on the facts endpoint.
If you add a formatting parameter after `value`, like "9,999", the query won't fail. Not sure if that's a desired behaviour.
*There is a disabled unit test with this ticket id. It has to be enabled once this is fixed.*
fails for rows on which we apply the to_string function. We also need to make sure that there are no other schemas that might throw errors because of this.
This can be reproduced with this query:
{code:java} ["extract", [["function", "to_string", "value"]], ["=","name", "uptime_seconds"]] {code} on the facts endpoint.
If you add a formatting parameter after `value` mask, like "9,999", the query won't fail, but no result is given. Not sure if that's Do we need a desired behaviour. default formatting mask for integers?
*There is a disabled unit test with this ticket id. It has to be enabled once this is fixed.*
fails for rows on which we apply the to_string function. We also need to make sure that there are no other schemas that might throw errors because of this.