Splunk Search

Why does "mvexpand X" remove events with X=NULL?

macoo
Explorer

Why does mvexpand X remove events with X=NULL? As simple as that. It's illogical from my perspective, unless it's on purpose.

thank you!

Tags (1)

woodcock
Esteemed Legend

Either way of behaving makes some sense but, IMHO the way that it actually work makes more sense than the other.
Either way it could have worked, could easily be converted to the other.
In this case, just do this:

... | eval X = coalesce(X, "ImpossibleValueToDropLater")
| mvexpand X
| eval X = if(X="ImpossibleValueToDropLater", null(), X)

nick405060
Motivator

You're the best! Thanks. I decided to write less code but convert null values to strings, as posted in https://answers.splunk.com/answers/548304/mvexpand-gives-less-results.html:

eval username=coalesce(username,"") | mvexpand username
0 Karma

woodcock
Esteemed Legend

If this worked for you, click "Accept" to close the question.

0 Karma
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...