By prepending an optional, non-capturing field splitter to our scanning regexp
we ensure that a valueless key is fully consumed, preventing a multibyte field
splitter from partially leaking into the next key.
Correctly parses out k1 => v1 and k2 => v2 from any of the following
sequences using the field splitter __:
By prepending an optional, non-capturing field splitter to our scanning regexp we ensure that a valueless key is fully consumed, preventing a multibyte field splitter from partially leaking into the next key.
Correctly parses out
k1
=>v1
andk2
=>v2
from any of the following sequences using the field splitter__
:Co-authored-by: Tom Gregory thomas.gregory@elastic.co