-
Notifications
You must be signed in to change notification settings - Fork 1
[LFXV2-882] Fix date parsing to log warnings instead of returning errors #19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not related to the change you made, but I'm assuming our source data is kinda inconsistent with the dates, so maybe we could try different date formats to actually get the data into v2 as much as possible.
Here's an example (not elegant at first glance, I know, but it works when the source doesn't follow a pattern):
Maybe this could be a backlog ticket.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's a good idea, though in this case somehow that field actually got the value
left the meeting. Reason : left the meeting(the leave reason being stored as the leave time, not sure if it's itx-zoom's fault or bad data in the Zoom webhook itself.Also I believe Meltano is actually be doing some date normalization already. I just checked the autodetected/built Dynamo ingest scheme, and these are getting considered as
datetimefields—and while we turned off schema validation for Dynamo-replicated data, because it was so inconsistent—meaning individual fields are coming across with different schemas, so some records will be a "string" instead of a "datetime"—the ones that do get parsed as a datetime are, I believe, converted to pythondatetime.datetimein transit, and then back to JSON.