- Notifications
You must be signed in to change notification settings - Fork 25.6k
Closed
Description
Especially in the logging case, it is common to have mappings with some inconsistencies yet these fields are never used in the result, e.g.:
SELECT longitude, latitude, dateTime FROM "mike_location*" ORDER BY dateTime LIMIT 1returns
Unexpected error from Elasticsearch: [verification_exception] Found 1 problem(s) line 2:6: [mike_location*] points to indices with incompatible mappings; field [previous_location] is mapped in [2] different ways: [object] in [mike_location], [geo_point] in [mike_location-v2]
While the message is correct, note that the problematic fields are not used.
Such queries should be allowed since the problematic fields are never used and thus can be safely ignored.