Skip to content
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

Validate Airbyte Json Message against the declared catalog #8596

Closed
Tracked by #8400
ChristopheDuong opened this issue Dec 7, 2021 · 2 comments
Closed
Tracked by #8400

Validate Airbyte Json Message against the declared catalog #8596

ChristopheDuong opened this issue Dec 7, 2021 · 2 comments
Labels
area/connectors Connector related issues autoteam team/extensibility technical-debt issues to fix code smell type/enhancement New feature or request

Comments

@ChristopheDuong
Copy link
Contributor

ChristopheDuong commented Dec 7, 2021

Tell us about the problem you're trying to solve

When a source emits a record data, we should be able to make sure it validates against the JSON schema or downstream process expecting certain types for example may fail.

Describe the solution you’d like

When writing a record to the destination, we should be able to validate the record and make sure it follows the specifications of the source connector. (this will not always be caught by acceptance tests because it depends on the content of the source database or API version)

@sherifnada sherifnada added area/connectors Connector related issues and removed needs-triage labels Dec 9, 2021
@girarda girarda added the technical-debt issues to fix code smell label Dec 22, 2022
@girarda
Copy link
Contributor

girarda commented Dec 22, 2022

@sherifnada we good to close this since this is done by the platform?

There might be a case for doing additional validation from the connector builder or for enforcing TypeTransforms but I think it should be tracked in more specific issues

@sherifnada
Copy link
Contributor

yup!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues autoteam team/extensibility technical-debt issues to fix code smell type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants