-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Source Stripe: fix stream schemas #21858
Source Stripe: fix stream schemas #21858
Conversation
/test connector=connectors/source-stripe
Build PassedTest summary info:
|
"start": { | ||
"start_date": { |
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.
I'm interested to know why a failing test didn't catch this before? Is it because we have yet to test this stream with expected_records?
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.
We can potentially test it with expected records if we strictly compare records. If not, then we allowed by default to have additional fields that not specified in schema. We currently have task to migrate to stripe tests to strict level (assigned to me) so I can check it during migration
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.
We currently have task to migrate to stripe tests to strict level (assigned to me) so I can check it during migration
Does this imply that we intend to have all the fields in the schema, but we just missed this one? (And the future test work will help us catch it faster?)
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.
I just have remembered that migration did not catch it properly with expected records :)
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.
I just have remembered that migration did not catch it properly with expected records :)
Can you please file a bug about this then?
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.
@evantahler @mfsiega-airbyte I'm not sure this is actually a bug. A missing field may be not spotted by the test because we guarantee that additionalProperties
field always equals True
. Do you think we should override this requirement when testing if data matches its schema? if yes, I will create an issue for that.
Another thing is that we have lots of streams not filled with data so the test is just skipped. This should be fixed for GA connectors when they all have a test strictness level set to high
One question: the report here mentioned at least one other field missing ( |
/test connector=connectors/source-stripe
|
Bumped a major version because of schema changes |
/test connector=connectors/source-stripe
Build PassedTest summary info:
|
@mfsiega-airbyte I added |
/publish connector=connectors/source-stripe if you have connectors that successfully published but failed definition generation, follow step 4 here if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-stripe
if you have connectors that successfully published but failed definition generation, follow step 4 here |
will merge this one when @klsoper approves |
Airbyte Code Coverage
|
What
https://github.com/airbytehq/oncall/issues/1364
How
Fix stream schemas:
for subscription stream,