On 10/25/2019 1:48 PM, rhys J wrote:
Is there some reason that text_general fields are returned as arrays, and
other fields are returned as hashes in the json response from a curl query?
<snip>
Here's the response:
<snip>
"dl2":["Great Plains"],
"do_not_call":false,
There are no hashes inside the document. If there were, they would be
surrounded by {} characters. The whole document is a hash, which is why
it has {} characters. Referring to the snippet that I included above,
dl2 is mapped in the hash to an array, and do_not_call is mapped to a
boolean, not a hash.
When there is an array in search results, it happens because the field
is multiValued ... even if there is only one value, it is placed in an
array for consistency.
Thanks,
Shawn
