@Abhishek Agarwal looking over the article, it doesn't really resolve this issue though. It was more there's no obvious way to convert a COMPLEX value type that is actually holding an array to a MV in the first place. For now, I've modified the ingestion to promote the array values to a first-child key in the incoming json payload. This means the SQL ingestion automatically identifies them as MV strings. However, if they're left lower in the JSON (very much preferable for dynamic payloads) then when using a JSON function to select the property, it's a COMPLEX.