Hello. Is there any problems `metadata_aspect_v2` ...
# feature-requests
m
Hello. Is there any problems
metadata_aspect_v2
is not stored in ElasticSearch? If it's possible, the deployment will take a huge step further by reduce an external dependency (MySQL/PostgreSQL).
b
Interesting request! I think it definitely could be done, we'd just need an impl of EntityService that uses Elastic.. and would need to also provide guidance about the backup and restore process 🙂 cc @mammoth-bear-12532 @green-football-43791
🚀 4
c
And preferably also an easy way to export from it. We are currently having a compliance mechanism based on dumps from our aurora backend.
b
Yep^^
Currently the nice thing about MySQL is that it can serve as a source of truth from which the downstream indices in elastic can be rebuilt in the case of data loss
⬆️ 1
If we centralize, we add a level of risk
m
what if data in mysql also is also lost?
m
there's generally better backup facilities available for db-s like mysql .. most companies treat them as source of truth
plus1 1
m
It's true. But I think it's better to let end-users decided what they wanna go, simplicity or guarantee 🙂
b
fair!
Would definitely be open to a contribution with an implementation of EntityService for elastic
🚀 2
l
Hello! this has been migrated to our new feature request portal https://feature-requests.datahubproject.io/b/Developer-Experience/p/store-metadata_aspect_v2-in-elasticsearch CC: @rapid-sundown-8805 @mysterious-monkey-71931 @stale-jewelry-2440 @bland-orange-95847 please head over there to upvote if this is still relevant to you!
👍 1
🚀 1