🚨🚨🐛 Source Mailchimp: Multiple schema updates and fixes

[ChristoGrab]

What

This PR introduces multiple breaking changes to Source Mailchimp's schema:

Timestamp fields have been updated from string to airbyte-type timestamp_with_timezone. In order to accommodate this change, empty string values are now converted to null for incremental streams. This is necessary as there are multiple timestamp fields which, when they do not contain a value, will be returned as empty strings by the API, causing validation errors on the declared date-time format.

The ._links field, which contains non-user relevant Mailchimp metadata, has been excluded from all requests, and removed from our schema (it was only declared in the Automations schema). This field was already being excluded from recently added streams, and since this update already constitutes a breaking change, now is a good time to filter it out entirely.

Docs updates

• Updated Prerequisites and added API Key setup steps
• Added HideInUI tags to non-setup sections, and collapsible Troubleshooting section
• Merged sync modes/streams lists into unified table

Misc

• Added suggested streams based on usage reports from Metabase.
• Moved logic to remove non-user relevant ._links field from individual stream implementation to base MailchimpStream class request_params.
• Refactored individual stream implementations of nullifying empty string fields to base IncrementalMailchimpStream class
• Removed a duplicate stream_state object in integration_tests/state.json
• Updates to expected records

🚨🚨 User Impact

Due to the changes in type to all timestamp fields, and the removal of the ._links fields from the schema, this is a breaking change affecting all Incremental streams. Customers will have to refresh their schemas and reset data in order to upgrade.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 19, 2023 10:40pm

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[tolik0]

@ChristoGrab Can you please add type for the /properties/recipients/properties/segment_opts/properties/conditions/items field in the automations stream?

[katmarkham]

"2024-01-10"

[ChristoGrab]

Updated 👍