not sure if this is a bug, but to me it seems like that:
Following scenario: I tried to encode strings with SHA1 within a preparatoin recipe and found that several outputs got the same hash, even though the input string varied.
I finally got closer to the cause, that in some cases the input value had a notation like: "3151E19012".
Using the toBase64 encoding and decoding (fromBase64) showed the value "Infinity".
I guess that Dataiku interprets the value as integer and not as string and therefore the number 3151E19012 is interpreted as exponential number that is out of range and returns the value Infinity to the function.
Is this a known issue?
Hi @Clément_Stenac ,
thanks for the quick response. 😊
I enforced that by converting the input with toString() first
Here's how the input looks:
The output looks as following:
This should be reproducable.
For the moment I have a workaround with an regular expression that splits the string. But in general the behaviour shouldn't be like that.
OK, I hadn't understood that you wanted to use it in a formula.
You will need to use strval("CY_MANUFACTURER_REFERENCE") instead of just CY_MANUFACTURER_REFERENCE
This is explained here: https://doc.dataiku.com/dss/latest/advanced/formula.html#variables-typing-and-autotyping
This behavior will not be changed: