validate eventTime field in python client

[pawel-big-lebowski]

Signed-off-by: Pawel Leszczynski leszczynski.pawel@gmail.com

Problem

eventTime field of a RunEvent is a non-validated string field in Python client, which is error-prone.

Closes: #2270

Solution

Validate date time on a python side.

Note: All schema changes require discussion. Please link the issue for context.

• Your change modifies the core OpenLineage model
• Your change modifies one or more OpenLineage facets

If you're contributing a new integration, please specify the scope of the integration and how/where it has been tested (e.g., Apache Spark integration supports S3 and GCS filesystem operations, tested with AWS EMR).

Checklist

• You've signed-off your work
• Your pull request title follows our guidelines
• Your changes are accompanied by tests (if relevant)
• Your change contains a small diff and is self-contained
• You've updated any relevant documentation (if relevant)
• You've updated the CHANGELOG.md with details about your change under the "Unreleased" section (if relevant, depending on the change, this may not be necessary)
• You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
• You've added a header to source files (if relevant)

---

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2022 contributors to the OpenLineage project

[JDarDagran]

Let's use dateutil isoparse method instead of this complex regex. It adds one dependency to Python client.

[pawel-big-lebowski]

Let's use dateutil isoparse method instead of this complex regex. It adds one dependency to Python client.

The Java definition on the server side of ZonedDateTime says:

A date-time with a time-zone in the ISO-8601 calendar system, such as 2007-12-03T10:15:30+01:00 Europe/Paris.

And this is failing when only a date in ISO-8601 provided. Dates like 2007-12-03 were the initial cause of the issue. The Python isoparse documentation claims:

An ISO-8601 datetime string consists of a date portion, followed optionally by a time portion

The term optionally is a problem I believe.

[JDarDagran]

The Java definition on the server side of ZonedDateTime

I think that's the thing. It's server side, not included in spec. So either we change spec ("format": "date-time" in jsonschema applies to RFC 3339 does not have zones as in ZonedDateTime) or stick to what we have and use dateutil which is then enough for sure.