👋 @adventurous-air-87342: did you have questions about k-v store?

yes

Why MySQL as K-V store vs dedicated K-V store?

<!here> 📣 Videos from the Town-hall are now uploaded to YouTube! • Full video: (includes release 0.8.0 highlights, roadmap and the content below) • Demo: Product Analytics design sprint: • Use-Case: DataHub on GCP at Confluent: • Deep Dive: No Code Metadata Engine:

nice to see you here @rapid-toothbrush-67483!

Welcome @fresh-carpet-31048!

<!channel> 📣 This is the announcement you have all been waiting for! We have officially released version 0.8.0 of DataHub.  Highlights • No Code Metadata: Add or extend an Entity model in < 15 minutes. This is a breaking change! We’ve provided an upgrade script + documentation to help manage migration.  • Slack Support Channel: Join #release-0_8_0 for upgrade support.  • Read the full announcement in the release notes. Video of No Code demo Here's to smooth upgrades for all 🏄

Hey folks! 🛑 We are aware of a few issues that have been reported and are working through them currently. Hold off on the upgrade until we give the green signal here!

<!here> Hello everyone!!! 🟢 We just cut a new release 0.8.1 (https://github.com/linkedin/datahub/releases/tag/v0.8.1) that fixes all the upgrade and install issues that we've observed in the last 24 hours. Please move to using it and give us your feedback! Continue using #release-0_8_0 for any troubleshooting. We will be monitoring it closely over the weekend. cheers!

.

<!here> This is happening tomorrow!

<!here> happening in 1 hour!

<!here>: starting now 🙂 https://zoom.datahubproject.io

Ideas around integration with query logs / usage logs -> ping @gray-shoe-75895

Simplification of Deployment -> raspberry pi hack day anyone? Ping @big-carpet-38439 🎉

and finally: Elasticsearch for Graph -> ping @green-football-43791 and @early-lamp-41924

and received error

{"exceptionClass":"com.linkedin.restli.server.RestLiServiceException","stackTrace":"com.linkedin.restli.server.RestLiServiceException [HTTP Status:400]: Parameters of method 'ingest' failed validation with error 'ERROR :: /entity/value :: \"com.linkedin.metadata.snapshot.ServiceSnapshot\" is not a member type of union [ { \"type\" : \"record\", \"name\" : \"ChartSnapshot\", \"namespace\" : \"com.linkedin.metadata.snapshot\", \"doc\" : \"A metadata snapshot for a specific Chart entity.\", \"fields\" : [ { \"name\" : \"urn\", \"type\" : { \"type\" : \"typeref\", \"name\" : \"ChartUrn\", \"namespace\" : \"com.linkedin.common\", \"doc\" : \"Standardized char 
----

@green-football-43791 @early-lamp-41924 ^

@big-carpet-38439 as well ^

This model should not be in the repository. We are raising a PR to remove it

@early-lamp-41924 ^

Yes. APIs are modeled within LinkedIn @mammoth-bear-12532 can comment more

The "Elastic for Graph" thing sounds interesting. Is there a migration script to move from Neo4J to ES?

@high-hospital-85984 one of my team was interested in adding DGraph as another alternative

Also, public service announcement: #release-0_8_x is the channel folks can use to discuss issues with using / upgrading with the current release line.

@big-carpet-38439 ^

Followed the instructions per this documentation on Rest.li - https://linkedin.github.io/rest.li/start/step_by_step#step-4-build-and-run-the-server and created a API schema (for the server response) and implemented a Restli resource just extending

CollectionResourceTemplate

but when hitting the curl on Step4 returns

No root resource defined for path '/aspects'

Any other ways to debug this?

Repost for higher visibility.

Hey Datahub Community, my company is looking to hire remote developers and data engineers with Datahub experience. I don't see a hiring channel which is why I am posting here. Please DM for recommendations or applications.

@early-lamp-41924 @big-carpet-38439 notes from our discussion • If gms is not running the user profile does not show up in frontend • on user profile page there is no user name • there does not seem to be a way to pass schema registry credentials for confluent cloud. schema registry and kafka cluster have different API credentials in confluent cloud. • kafka setup guide needs some improvement