topic Re: Round problem in Splunk Search

Round problem

lukasz92 — Mon, 28 Sep 2020 18:16:34 GMT

When I enter this query:

I get -nan in columns when second parameter of round function is less than -2.
When -2 , everything is rounded to the -2 place after the dot (it equals second place beforce the dot)

Could you explain why?
Is this bug or a feature? 🙂

Re: Round problem

Ayn — Fri, 28 Nov 2014 13:03:07 GMT

What's the idea with supplying a negative integer there at all?

Re: Round problem

lukasz92 — Fri, 28 Nov 2014 13:42:53 GMT

negative integer after a dot = positive integer before a dot - isn't it logic?
I want to round a number to thousands (1345 -> 1000 ; 1501 -> 2000).
Syntax round(1345/1000,0)*1000 is uglier

Re: Round problem

richgalloway — Fri, 28 Nov 2014 14:06:46 GMT

The documentation for the round() function does not mention use of negative values for the second argument. Based on that and your experience, I conclude they are not supported.

Re: Round problem

martin_mueller — Fri, 28 Nov 2014 23:19:23 GMT

To get around the syntax ugliness you can define a macro round(2) with arguments $x$,$y$ as (round($x$*pow(10,$y$))/pow(10,$y$)) and call that like this:

... | eval time2 = `round(_time, -3)` | ...

Re: Round problem

lukasz92 — Mon, 01 Dec 2014 11:23:53 GMT

Solution works, but I think this is a faulty function.
Could I trust "pow", or there are another crazy limitations I don't know? 😕

It is not documented what the second parameter should look like,
@richgalloway comment should definetly appear in the official documentation.

Re: Round problem

Ayn — Mon, 01 Dec 2014 12:05:36 GMT

I disagree with that interpretation. The documentation states:

This function takes one or two numeric arguments X and Y, returning X rounded to the amount of decimal places specified by Y.

It makes no sense in this context to mention negative integers at all.

Re: Round problem

lukasz92 — Mon, 01 Dec 2014 12:23:27 GMT

Shouldn't args be tested for invalid values?