Splunk Search

Math function return only 17 most significant digits

jeromesauve
Engager

Hello everyones,

Every math operations or functions seem to round the number to the 17th most significants digits.

To showcase the problem, I have made a test lookup table that look like that:

id, long_numbers
1, 12345678901234567894
2, 12345678901234567814
3, 12345678901234567826

If I run this :

|inputlookup test_long_numbers.csv
|eval should_be_the_same=(long_numbers*1)

The results in the new column are automaticly rounded like that:

id long_numbers should_be_the_same
1 12345678901234567894 12345678901234567000
2 12345678901234567814 12345678901234567000
3 12345678901234567826 12345678901234567000

The min(), max(), avg() used with stats all have the same behaviour.
Does someone know why it's acting like that and
if there a way to prevent this behaviour?

Thanks,

Jérôme-A. Sauvé

Tags (1)
0 Karma

jplumsdaine22
Influencer

I'm guessing thats because the data type is a 64 bit signed doubles , so theres a maximum amount of precision.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...