Hi all, we recently updated to 0.8.31 to take adva...
# troubleshoot
p
Hi all, we recently updated to 0.8.31 to take advantage of the impact analysis feature as shown in the demo. As seen in the picture, it looks like we are still missing the impact analysis button. Just wondering if there's a config or something we have to enable to get this functionality Thanks!
e
Hey! Which graph service backend are you using? We only support elasticsearch right now. Neo4j will come in the next quarter!
p
Ahhh we are using neo4j - but i don't think we'd be opposed to using elasticsearch any trade offs there?
e
There are not much trade offs as of now, but some of the folks wanted more complicated multi node to multi node path finding operations, which is very inefficient in elasticsearch. All existing DataHub supported features like lineage works well on ES and its one less component to manage
p
Awesome, appreciate it!
Looks like the restore indices cron job failed with:
Copy code
Failed to find Entity with name container in Entity Registry: java.lang.IllegalArgumentException: Failed to find entity with name container in EntityRegistry
Failed Step 3/3: SendMAEStep. Failed after 0 retries.
Exiting upgrade RestoreIndices with failure.
Upgrade RestoreIndices completed with result FAILED. Exiting...
Can create a new post for this if needed
e
Hey so
does the datahub-upgrade container have the same version as gms?
p
hey @early-lamp-41924 looks like the upgrade container is way behind: acryldata/datahub-upgrade:v0.8.22.0 we use helm for our deployments, is there something special we need to be doing to ensure that container is updated?
nvm, mistake on our end
e
Glad its not the case! Was worried for a sec