Mixpanel Migration Guide
Upgrading to 3.0.0
In this release, we introduce breaking change for CohortMembers
stream:
- State is changed to per-partition format.
- Key is changed to correct unique key (based on 'distinct_id' and 'cohort_id' fields) since previous key was not unique and didn't support possibility for user be in a few different cohorts.
Semi-incremental
Cohorts
,CohortMembers
andEngage
streams with client-side filtering extract records since user provided or default (1 year old) start_date.
To gracefully handle these changes for your existing connections, we highly recommend resetting your data before resuming your data syncs with the new version.
Migration Steps
For Airbyte Open Source: Update the local connector image
Airbyte Open Source users must manually update the connector image in their local registry before proceeding with the migration. To do so:
- Select Settings in the main navbar.
- Select Sources.
- Find
Mixpanel
in the list of connectors.
You will see two versions listed, the current in-use version and the latest version available.
- Select Change to update your OSS version to the latest available version.
Update the connector version
- Select Sources in the main navbar.
- Select the instance of the connector you wish to upgrade.
Each instance of the connector must be updated separately. If you have created multiple instances of a connector, updating one will not affect the others.
- Select Upgrade
- Follow the prompt to confirm you are ready to upgrade to the new version.
Refresh affected schemas and reset data
- Select Connections in the main nav bar.
- Select the connection(s) affected by the update.
- Select the Replication tab.
- Select Refresh source schema.
- Select OK.
Any detected schema changes will be listed for your review.
- Select Save changes at the bottom of the page.
- Ensure the Reset affected streams option is checked.
Depending on destination type you may not be prompted to reset your data.
- Select Save connection.
This will reset the data in your destination and initiate a fresh sync.
For more information on resetting your data in Airbyte, see this page.
Upgrading to 2.0.0
In this release, the default primary key for stream Export has been deleted, allowing users to select the key that best fits their data. Refreshing the source schema and resetting affected streams is necessary only if new primary keys are to be applied following the upgrade.
Upgrading to 1.0.0
In this release, the datetime field of stream engage has had its type changed from date-time to string due to inconsistent data from Mixpanel. Additionally, the primary key for stream export has been fixed to uniquely identify records. Users will need to refresh the source schema and reset affected streams after upgrading.