🚨🚨🐛 Source Mixapanel: Delete default primary key for Export stream

[tolik0]

What

Removed the default primary key from the Export stream.

How

The columns recommended by Mixpanel for the primary key - [insert_id, event_time, event_name, distinct_id] - may not always have an insert_id for certain users. This issue is discussed in detail here. This PR aims to give users the flexibility to choose their primary key, as requested in this related PR.

🚨 User Impact 🚨

This PR introduces breaking changes due to the removal of the default primary key for the Export stream.

[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	Nov 3, 2023 4:18pm

[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.

[katmarkham]

if ["distinct_id", "event", "time"] fits their usecase do they still need to refresh/reset?

[tolik0]

Thank you for pointing that out! Upon local testing, it was found that after upgrading, users have the option to change the primary key, and the previous fields remain selected. Therefore, a refresh is only necessary if there's a need to apply a new primary key. I've updated the relevant messages to reflect this.