Hi! We’re moving ahead with out PoC, and now we’re...
# getting-started
h
Hi! We’re moving ahead with out PoC, and now we’re wondering what the minimum/maximum supported version are for the databases: • MySQL or Postgres • Neo4J • Elasticsearch
Sorry, didn’t find any mention of this in the docs
Stumbled on this discussion: https://github.com/linkedin/datahub/issues/1722. So ES 6.X seems possible, but 5.X is the safer bet
b
You can check the docker files for recommended versions, e.g. https://github.com/linkedin/datahub/blob/master/docker/docker-compose.yml
Internally we're running • MySQL 5.7 • ES 5.5 (planning to upgrade to 7.x by EOY) • neo4j 4.0.6
h
okey thanks! Our worry is that ES 5.6 is EOL in March 2019 😬
Would the internal bump to ES 7.x require some time to trickle down to the open source code base?
b
Most likely. We'd prefer to battle test it before releasing it to OSS. That said, I believe someone in the OSS has already got it working. Need to dig through Slack and GH to find the conversation.
h
And shouldn’t be too difficult to test locally, i guess 🤷‍♂️
b
Should be fairly easy to test.
a
I have tested the latest MySQL, the latest ES and latest Neo4j. I only saw the
dataset-index.json
etc have some incompatibility issues, mainly syntax error of index definition, other than that, it seems work well.
👍 1
Have to take my word back. there are quite some code modification around ES in Datahub need to be modified for the latest ES.
h
okey, good to know!
b
@acceptable-architect-70237 care to do a PR if you get ES 7 working?
a
sure. Internally we are using ES 7 so everything has been figured out.
b
Awesome. @microscopic-waitress-95820 @microscopic-receptionist-23548 FYI
m
I mentioned on github, might be a bit different for us
We need to provide an upgrade path to 7, we can't just drop 5 😛
Not sure how LJ did it, if it just breaks 5 it is a no go. Though we can certainly take advantage of his work for a 7 implementation, we just might need to also have a 5 implementation for a bit, sadly
a
internally we only use es7 so yes, my implementation didn't support ES 5. It seems it is not easy to support both in code level. I saw some people does that in package level (also easier to drop the support to a certain version totally) down to the road. based on how datahub modules are organized, package level might not be realistic.