You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally created by @vischous on 2021-09-29 15:04:43
Summary
Validate tap data schema, particularly useful during development as right now you have to add a target that does this validation ie meltano elt tap-abc target-jsonl jsonl will validate for you. Maybe it should stay like this?
Proposed benefits
One less step while doing development, the issue I'm seeing is running production data through a tap I'm writing leads to a bunch of Data in a format that wasn't expected (String is sometimes an Int, or something it's an array of Strings, etc etc).
Theoretically you could suggest a new schema for the stream that's causing issues.
Proposal details
A --validate option
Standard validate_json config
Best reasons not to build
You could offload this to a target
People may forget to turn this off in production which would have performance implications
This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen label, or request that it be added.
Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/228
Originally created by @vischous on 2021-09-29 15:04:43
Summary
Validate tap data schema, particularly useful during development as right now you have to add a target that does this validation ie
meltano elt tap-abc target-jsonl
jsonl will validate for you. Maybe it should stay like this?Proposed benefits
Proposal details
A --validate optionStandard validate_json config
Best reasons not to build
Use Cases
The text was updated successfully, but these errors were encountered: