A complete solution for open data platforms, enterprise data catalogs, data lakes and data management. Open source, mature, fully-featured and production ready.

DataHub

Folks folks folks, I'm back with the second installment of the GraphQL frontend API proposal covering... you guessed it: mutations!

Feel free to take a look and let me know your thoughts: <https://github.com/linkedin/datahub/pull/2047>

In addition, I've updated the reference implementation PR to include example impl paths for writing entities, along with auth, search, &amp; browse capability: <https://github.com/linkedin/datahub/pull/2044/commits/4f77ecfffe19871b8ae709629500b083e85f4ac0>

Note that the reference impl is still evolving--- feel free to leave thoughts anyways! One major item on my list: Generate strongly typed POJOs from the GQL schema to avoid all of those ugly maps

I have a theory that we should eventually be able to generate Resolvers auto-magically also... depending on the modeling convention..

On this topic - This is the most promising thing ive found: <https://github.com/kobylynskyi/graphql-java-codegen/tree/master/plugins/gradle>.. Little concerned about low engagement community but it's recommended by official graphql-java github...