Ingesting JSON data into a realtime table. A field in the JSON is a JSON string with leading spaces but is always numeric data otherwise:

{ "account":"      123", .....}

If my realtime table defines the account column as DOUBLE, then the record loads with no issue -- the spaces appear to be ignored. However, if I define the column as INT then the record does not load. More troublesome, I can't find any error messages in any of the logs -- I would expect some kind of error message?

Thanks for reporting @Josh Highley, let me take a look at the code, and will get back to you

No, unfortunately, it's not practical for us to parse the record prior, modify the value, then write it out again.

Thanks for submitting the issue.

@Mayank so jave trims the string for double parse but not for integer parse?

Yes

That’s bizarre. Should be a simple fix but might add perf overhead for things that are already trimmed may be try trim only on exception?

This was a standalone unit test that I did, I'll take a look at where in the code we do the type conversion a little later.