scottklement.com

In my case I need the null to not get loaded into the database as *NULL and I'm dealing with an extremely complex JSON doc so I need it to not load the nulls at all. You're correct though the real issue appears to be with the skip_nulls option itself when the last element in a structure that is part...

Absolutely. Here's a sample of the JSON that will cause the issue. Sample JSON Doc { "documents": { "test_doc1": [ { "element1": "value1", "element2": "value2" } ], "test_doc2": [ { "element1": "value3", "...

One quick update on this. I realized that the issue only occurs if the last element in the first array occurrence contains a null value. I was using the "skip_nulls" option to avoid issues with null values but removing that and replacing it with "value_null": "" to repl...

Thanks for the response. The JSON doc I used along with the RPG Data Strucure are both just examples so the format may be wrong, however the actual doc (which I can't easily share because it contains proprietary information and PII) are properly formatted JSON. What has me confused is I only see the...

I have an application that accepts documents that contain JSON arrays, which are in turn loaded into data structure arrays. The application works fine as long as the JSON array only contains a single element but when it has more than one element DATA-INTO using YAJLINTO throws "The information ...