I'm working on upgrading from DataHub 0.8.1 to 0.8...
# troubleshoot
o
I'm working on upgrading from DataHub 0.8.1 to 0.8.8. As part of that upgrade, I'd like to drop Neo4j. I'm using the helm chart at https://github.com/acryldata/datahub-helm. Is it correct to assume that if I want lineage to work after running this upgrade, I'll need to run the
RestoreIndices
upgrade manually after
helm upgrade
? (details in thread)
I'm fairly sure, from https://github.com/linkedin/datahub/tree/fef2ea7126b41405aea935c572450a03c4780e8a/docker/datahub-upgrade, that
RestoreIndices
is the thing I want to populate Elasticsearch with the type of data that was previously in neo4j.
RestoreIndices: Restores indices by fetching the latest version of each aspect and producing MAE
but I don't see a way to get that run in a job by the
datahub
helm chart. There is this
datahubUpgrade
section in the chart's
values.yaml
https://github.com/acryldata/datahub-helm/blob/648c3b6f44287db0efacf8ff14e044dc9bec88ae/charts/datahub/values.yaml#L52-L58 But it isn't documented at https://github.com/acryldata/datahub-helm/blob/648c3b6f44287db0efacf8ff14e044dc9bec88ae/charts/datahub/README.md or anywhere else I've been able to find.
g
Hey there! Fortunately, you should not need to also run restore indices.
Part of the upgrade involves resetting the graph indices.
o
blegh sorry, I JUST found it https://github.com/acryldata/datahub-helm/blob/648c3b6f44287db0efacf8ff14e044dc9be[…]plates/datahub-upgrade/datahub-restore-indices-job-template.yml and I can see from
helm template
that that job is going to be included. Ok cool cool, As always, thanks for the quick response and sorry for the noise.
g
Just make sure that you start up with graph_service set to elastic
o
don't you hate when you type out a question and then think of one more thing to try RIGHT AFTER. ugh
g
no problem! glad you are sorted out 🙂
thankyou 1