Upgrade Issues from v0.3.11.1 to v0.3.12.1

Users experienced problems when attempting to upgrade their DataHub instance from version 0.3.11.1 to 0.3.12.1. The upgrade process would fail or result in degraded functionality, potentially related to schema migrations, Elasticsearch reindexing requirements, or incompatible configurations between versions.

You Might Be Asking:

• What are the prerequisites for upgrading to v0.3.12?
• Why is my upgrade failing?
• Do I need to reindex after upgrading?

The upgrade path from v0.3.11.1 to v0.3.12.1 requires specific steps to ensure compatibility. Follow the proper upgrade procedure:

1. Review Breaking Changes: Check the release notes for v0.3.12 for any breaking changes
2. Backup Your Data: Create backups of your metadata store and Elasticsearch indices
3. Update Helm Values: Ensure your Helm values are compatible with v0.3.12
4. Run System Update Job: Allow the system update job to complete migrations
5. Verify Elasticsearch Settings: Check zone awareness and reindex optimization settings

# Update Helm chart
helm repo update acryl-datahub
helm upgrade datahub acryl-datahub/datahub \
  --version 0.3.12.1 \
  --values your-values.yaml

# Monitor system update job
kubectl logs -f <system-update-job-pod>

Fixed in version v0.3.12.1. If you have Elasticsearch clusters with zone requirements, set global.elasticsearch.index.upgrade.reindexOptimizationEnabled to false in your Helm values. Remote executors must be updated to v0.3.12 or later before upgrading the main DataHub instance.

• Updating DataHub
• Kubernetes Deployment