-
EnvironmentDelta-rs version: Binding: Environment:
BugWhat happened: I THINK the error is happening when the engine fails to write the items. It then creates a log item in s3 with no creationTime like below which BigQuery is unable to parse and then the complete table is failing to load. I don't know if this is expected behaviour from the lib and it's just BigQuery that is not reading the metadata correctly or if this actually is a bug in the lib. I CAN read the table when using the Python client, just not with BigQuery. Any advice here would be highly appreciated. What you expected to happen: How to reproduce it: More details: |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
It's an optional field so that's something google needs to address in bigquery |
Beta Was this translation helpful? Give feedback.
-
|
@Petterhg as @ion-elgreco mentioned #2926 does ensure that the |
Beta Was this translation helpful? Give feedback.
@Petterhg as @ion-elgreco mentioned
createdTimeis optional but unfortunately some delta implementations do not treat optional as actually optional 😭#2926 does ensure that the
createdTimegets set when a new metadata action is created, such as on schema evolution, so perhaps once I release 0.20.2 you would be able to modify the schema of that table or recreate it in order to make it BigQuery readable?