Just went through upgrading to the most recent hel...
# all-things-deployment
f
Just went through upgrading to the most recent helm release (v0.8.32 and I don't seem to have the lineage impact assessment? Shouldn't this have been included in v0.8.28?
screenshot:
l
Hello @fancy-fireman-15263 This seems to be related to the graph service used https://datahubspace.slack.com/archives/C029A3M079U/p1647631344451309?thread_ts=1647631014.330189&cid=C029A3M079U
f
So I'd need to migrate over to elasticsearch or wait until the neo4j work is done correct?
l
I think yes.
Maybe a member of the core team can confirm
I’m in the same situation as you, I don’t have access to this feature
e
This is correct. We are planning to implement the neo4j version in Q2!
f
Are there docs for the neo4j -> ES migration?
e
Yes! Here is a more detailed doc on running the restore indices job https://datahubproject.io/docs/how/restore-indices/
f
Yeah all sorted now
👍
@loud-camera-71352 just redeploy with
graph_service_impl: elasticsearch
in the values.yaml then run:
Copy code
kubectl create job --from=cronjob/datahub-datahub-restore-indices-job-template datahub-restore-indices-adhoc
teamwork 1
e
Awesome!!!