Ultimate access to all questions.
Downstream consumers of a Delta Lake table are reporting data quality issues affecting their application performance, particularly due to invalid latitude and longitude values in the activity_details
table. A junior engineer attempted to add CHECK constraints with the following code, which fails despite correct logic for valid coordinate ranges (-90 to 90 for latitude, -180 to 180 for longitude):
ALTER TABLE activity_details
ADD CONSTRAINT valid_coordinates
CHECK (
latitude >= -90 AND
latitude <= 90 AND
longitude >= -180 AND
longitude <= 180
);
What is the reason for this execution failure?