I'm not sure if I fully understood the problem. The inconsistency is only triggered by missing values (like a null in either Longitude or Latitude) right?

If so, it doesn't seem particularly inconsistent as neither backend is going to include that Location in the results; in the ES case it could be found if one sets a very large search range (unless MAX_VALUE is treated as a special case).