Hi everyone, while I'm trying `datahub docker quic...
# all-things-deployment
n
Hi everyone, while I'm trying
datahub docker quickstart
, it seems my server can't reach GitHub due to my org's policy. So I'm about to try
datahub docker quickstart --quickstart-compose-file <path to compose file>
. And I can see there are two files from GitHub: 1. docker-compose-without-neo4j.quickstart.yml 2. docker-compose.quickstart.yml When I tried
datahub docker quickstart
, it tried to fetch the first one. If my server already has neo4j on it, then would it be better to use the second one? If I use the first one, then I can't use the graphical lineages?
📖 1
✅ 1
l
Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? 2️⃣ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? Did you find a solution to your issue?
n
I guess ES will be used by without-neo4j version and it is recommended.
b
the graphical lineage is viewable in datahub UI regardless of which graph implementation you used. (though not sure whats the diff in performance or was it just licensing considerations)