topic Re: json_extend Scalar Bug, or Coercing JSON Scalars into JSON Arrays in Splunk Search

json_extend Scalar Bug, or Coercing JSON Scalars into JSON Arrays

tscroggins — Sat, 13 Dec 2025 15:42:09 GMT

Hi Splunkers!

In the current json_extend documentation <https://help.splunk.com/en/splunk-enterprise/spl-search-reference/10.0/evaluation-functions/json-functions>, if <path> specifies "a scalar or object value," the value should be "[autowrapped] ... within an array;" however, this doesn't appear to be the case:

| makeresults
| eval obj=json_object("foo", "bar") ``` or obj="{\"foo\":\"bar\"}" ```
| eval arr=json_extend(obj, "foo", json_array("baz")) ``` or arr=json_extend(obj, "foo", "[\"baz\"]") ```

If I understand the documentation correctly, "bar" should be coerced to the array ["bar"] and then extended to ["bar","baz"], but it is not. The original object is returned unmodified. json_extend works correctly when the input value is already an array:

| makeresults
| eval obj=json_object("foo", json_array("bar", "baz"))
| eval arr=json_extend(obj, "foo", json_array("qux"))

The example was contrived to illustrate the issue. In practice, the value of foo may be either an array or a scalar. For example, the lookup eval function returns a scaler on a single match and an array on multiple matches. json_extract is similarly inconsistent when it returns a Splunk native type for scalars and a string for arrays:

| makeresults
| eval obj=json_object("foo", "bar")
| eval val=json_extract(obj, "foo") ``` ==> foo ```
| eval obj=json_object("foo", json_array("bar", "baz"))
| eval val=json_extract(obj, "foo") ``` ==> ["bar","baz"] ```

If scalars can be coerced into arrays, values that may be either scalars or arrays can be parsed by json_array_to_mv or other functions without custom wrappers using if, case, replace, etc.

Have you encountered this issue? How have you solved it?

Re: json_extend Scalar Bug, or Coercing JSON Scalars into JSON Arrays

PickleRick — Sat, 13 Dec 2025 20:21:51 GMT

I can confirm that it does indeed seem to work not as it is described in the docs. So it warrants a support case.

A walkaround would require some dirty trick with checking whether an element is a scalar or not (possibly with json_array_to_mv(json_extract(...)) and then do json_delete() and json_append(). Very ugly.

Re: json_extend Scalar Bug, or Coercing JSON Scalars into JSON Arrays

tscroggins — Sun, 14 Dec 2025 14:03:14 GMT

This is for me, not a customer; I only have a dev license.

Re: json_extend Scalar Bug, or Coercing JSON Scalars into JSON Arrays

PickleRick — Sun, 14 Dec 2025 14:10:08 GMT

You could post a docs feedback instead.

Re: json_extend Scalar Bug, or Coercing JSON Scalars into JSON Arrays

tscroggins — Sun, 14 Dec 2025 14:25:34 GMT

So much feedback for the new documentation SPA. 😉 Edit: I've posted feedback. Pre-Cisco, feedback was very effective; I've not submitted anything since the acquisition, so we'll see! Grammar and syntax have taken a downturn over the last year or so.

Re: json_extend Scalar Bug, or Coercing JSON Scalars into JSON Arrays

tscroggins — Sun, 14 Dec 2025 16:49:06 GMT

The "autowrap" functionality was introduced (according to documentation) in 9.2.0 <https://help.splunk.com/en/splunk-enterprise/search/spl-search-reference/9.2/evaluation-functions/json-functions>.

I just tested in 9.2.0.1, and the behavior is the same as 10.0. I'm not going to test every maintenance release between then and now, but I'd guess it's never worked as documented.