topic Re: Why does convert num NOT follow a universal typecasting paradigm and NOT trim leading zeroes? in Splunk Search

Why does convert num NOT follow a universal typecasting paradigm and NOT trim leading zeroes?

nick405060 — Tue, 06 Aug 2019 20:58:18 GMT

I guess the question is a bit facetious

But, I would still like to know what the (flawed) logic is behind this? It's like Splunk wants you to spend hours debugging or have poor data integrity.

| makeresults | eval test="06" | convert num(test) | eval test="".test | eval a=if(test="6","yes","WHY")

Re: Why does convert num NOT follow a universal typecasting paradigm and NOT trim leading zeroes?

nick405060 — Tue, 06 Aug 2019 21:05:44 GMT

PS for anyone looking for a workaround, not an explanation (which is what I am looking for in an answer), you can just use tonumber or ltrim etc

Re: Why does convert num NOT follow a universal typecasting paradigm and NOT trim leading zeroes?

somesoni2 — Tue, 20 Aug 2019 21:47:54 GMT

See this version of your query:

| makeresults | eval test="06" | convert num(test) | eval test="".test | eval result1=if(test="6","just 6","NA") , result2=if(test="06", "zero padded 6", "NA"), result3=if(test=6,"number 6", "NA")

Re: Why does convert num NOT follow a universal typecasting paradigm and NOT trim leading zeroes?

nick405060 — Tue, 20 Aug 2019 22:20:04 GMT

ugh

Re: Why does convert num NOT follow a universal typecasting paradigm and NOT trim leading zeroes?

diogofgm — Tue, 03 Sep 2019 17:10:51 GMT

Check this please:

| makeresults | eval test=tonumber("06") | eval a=if(test="6","yes, splunk can cast to number","WHY")

Re: Why does convert num NOT follow a universal typecasting paradigm and NOT trim leading zeroes?

nick405060 — Tue, 03 Sep 2019 18:27:58 GMT

Already noted in a comment on the question.