Not in this pull request; for us this changed the tokenizing behaviour into something that was more-correct for what receives logstash events on our side.  I think the right thing to do is have a config setting for the way to handle nil; maybe that's overkill, though, as we demonstrated, a one-line change fixed it right up for us.