"Luckily" the same bug exists in both indexing and querying. Unfortunately, because it is in indexing, it will require a version bump to fix and we would need to keep the old code around.

This also adds a relatively slight overhead because it is computing strlen rather than just using the size stored in the BSONElement. But that cost is trivial relative to the actual tokenization, so I don't think it is a good motivation alone to fix this.