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 Shopify: fix None
cursor field value, access_scopes
keyError issue, JSONDecodeError
issue, mark datefields
as format of date
#25110
Conversation
/test connector=connectors/source-shopify
|
None
cursor field value, access_scopes
keyError issuesNone
cursor field value, access_scopes
keyError issue, JSONDecodeError
issue, mark datefields
as format of date
/test connector=connectors/source-shopify
Build PassedTest summary info:
|
/test connector=connectors/source-shopify
Build PassedTest summary info:
|
/test connector=connectors/source-shopify
Build PassedTest summary info:
|
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.
Nice!
/test connector=connectors/source-shopify
Build PassedTest summary info:
|
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.
Approving with a Big caveat below.
Looking at our Connector Breaking Change Release Playbook it seems like this is a non-breaking change. But it "feels" like it close to it.
@bazarnov Can you confirm this meets none of this criteria below and if we released no user connections would be broken requiring action on their end.
If so then feel free to merge, if not please hold off.
Breaking changes
- Spec Change - The configuration required by users of this connector have been changed and syncs will fail until users reconfigure or re-authenticate. This change is not possible via a Config Migration
- Schema Change - The type of a property previously present within a record has changed
- Stream or Property Removal - Data that was previously being synced is no longer going to be synced.
- Destination Format / Normalization Change - The way the destination writes the final data or how normalization cleans that data is changing in a way that requires a full-refresh.
- State Changes - The format of the source’s state has changed, and the full dataset will need to be re-synced
@bnchrch
No impact is expected. Tested locally the transition from Publishing this now and merging it. Thanks for the review! |
/publish connector=connectors/source-shopify
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-shopify
if you have connectors that successfully published but failed definition generation, follow step 4 here |
…rror issue, `JSONDecodeError` issue, mark `datefields` as format of `date` (airbytehq#25110)
What
Resolves:
How
default_state_comparison
when the state has an explicit value ofNone
, whileget_updated_state()
access_scopes
could not be verified, because of bad credentialsAvailabilityCheck
and regularsync
)JSON Schemas
to satisfy the CAT requirements.format
for CAT and enabledhigh
strictness🚨 User Impact 🚨
This PR introduces non-breaking changes for stream schemas. Users likely to update their schemas should
reset the data
andre-sync
once again for selected streams.Pre-merge Checklist
Expand the relevant checklist and delete the others.
Updating a connector
Community member or Airbyter
Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.Code reviews completed
Connector version has been incremented
Dockerfile
has updated versionDocumentation updated
README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
with an entry for the new version. See changelog examplePR name follows PR naming conventions
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described here