OpenMetadata
laminar
OpenMetadata | laminar | |
---|---|---|
26 | 4 | |
4,140 | 23 | |
4.9% | - | |
10.0 | 0.0 | |
6 days ago | 5 months ago | |
TypeScript | TypeScript | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
OpenMetadata
-
How to Dynamically Adjust the Height of a Textarea in ReactJS
In this blog post, I have demonstrated how I addressed the challenge of dynamically adjusting the height of a textarea element based on its content, preventing the need for vertical scrolling in the title section of the OpenMetadata Knowledge article page.
-
Blog - Project Nessie: A Look in the Depths
How does this compare with https://github.com/open-metadata/OpenMetadata
-
What is your favorite data catalog?
u/cmcau try https://open-metadata.org much easier to setup , for details https://docs.open-metadata.org and for any support https://slack.open-metadata.org
-
Data Governance Hands On with Amazon DataZone
Then, a pool of tools appeared on the market with features that allow covering some of the challenges cited, especially those related to data cataloging. Informatica's tool is perhaps the best known among the licensed. Among the open source tools, I highlight Data Hub (www.datahubproject.io) developed on LinkedIn, Open Metadata (https://open-metadata.org/) and Amundsen (https://www.amundsen.io /) powered by Lyft. In addition to cataloging and discovering data artifacts, these tools allow for a view of data lineage, including technical documentation and business terms, and building relationships between data artifacts. Also, it is possible to register data owners, the people responsible for the data in those tools. This greatly facilitates access request and evaluation process (which today is a major bottleneck).
-
What OSS are you using for data contracts?
Probably, in order to have it integrate with tools like OpenLineage and OpenMetadata and such I will have to make open-source contributions.
-
Thoughts around decube.io (data observability and catalog platform)
We are the team behind OpenMetadata . Our mission is to build a centralized metadata platform that offers data discovery, collaboration, governance and quality. We believe that having tool for each of these categories not only result user frustration but metadata silos.
-
Great expectations?
As anyone ever tried open metadata for data QA testing? Curious about that https://open-metadata.org/
-
Our data catalog is difficult to manage and not built for the wider org - what can we do?
We're looking to PoC https://open-metadata.org/ shortly
-
Looking for an open-source data lineage app, where objects and connections can be manually defined (not just automatically ingested)
Hello everyone, I'm looking for an open-source data lineage app (e.g. tokern, datahubproject, openmetadata).
-
Ask HN: Do you use JSON Schema? Help us shape its future stability guarantees
We at OpenMetadata(https://open-metadata.org) use JsonSchema extensively to define the metadata standards. JsonSchema is one of the reasons we are able to ship and get the project to what it is today in quick time. More about it here https://www.youtube.com/watch?v=ZrVTZwmTR3k
laminar
-
Ask HN: Does Anyone Like GraphQL?
The main (and only) criticism I’ve ever heard about graphql in the companies I worked for was that it is very js-oriented all the best libs/frameworks for it are for react frontend / node server mostly.
Backend scala / php devs looked at it with distaste in their eyes, coming up with various reasons why its not a good idea.
And to be fair with tools like openapi / grpc a lot of the benefits of graphql can be replicated.
Even if they are clumsy and fragmented compared to it in my eyes, they still work well enough and keep devs in all camps happy enough, and compromise as they say is “when everyone is equally unhappy”.
Now placed in situations like this I am usually forced to reimplement graphql tooling with the chosen api tech (for example https://github.com/ovotech/laminar) and if me as a single dev could do it, then I’d wager if there was stronger tech leadership, all the other tech tribes could just smooth the edges that they didn’t like for using graphql in their respective languages … but sadly that has not been my experience.
-
Ask HN: Do you use JSON Schema? Help us shape its future stability guarantees
I use it extensively in prod. Well the superset that is OpenApi. It enables contract first development where any change to the api is done in the schema fist, and then implemented by the clients/server.
Since we have tooling[0] that validates requests and responses at runtime, the clients can be absolutely sure of what they receive (we through 500 if the server attempts to respond with an undocumented respond) And the server is also sure about the shape of the requests. This allows us to validate everything at compile time too, generating typescript types for both client and server.
And since we have similar tooling regarding our data stores (typescript types for sql queries) most of the time if there is a bug, the code would simply not compile - pretty nifty!
[0] - https://github.com/ovotech/laminar
- SQLBolt – Interactive lessons and exercises to learn SQL
-
Bad TypeScript Habits to Break This Year
If the api has some contract with it OpenApi / Swagger / etc, its surprisingly easy to write a parser that would convert those to typescript types. TS has an awesome use as a library itself where you can write the ast with, and then tell it to convert it to code.
We use it to great effect ourselves, by generating types for axios.
https://github.com/ovotech/laminar/tree/main/packages/lamina...
Now granted, you’re now trusting the api writers with their contract, but if its another team in the org we’ve found it to be warranted.
What are some alternatives?
datahub - The Metadata Platform for your Data Stack
pgtyped - pgTyped - Typesafe SQL in TypeScript
marquez - Collect, aggregate, and visualize a data ecosystem's metadata
fp-ts - Functional programming in TypeScript
odd-platform - First open-source data discovery and observability platform. We make a life for data practitioners easy so you can focus on your business.
schema-dts - JSON-LD TypeScript types for Schema.org vocabulary
Hyperactive - An optimization and data collection toolbox for convenient and fast prototyping of computationally expensive models.
alt-schema - Flat JSON Schema specification and basic utility methods
Deeplearning4j - Suite of tools for deploying and training deep learning models using the JVM. Highlights include model import for keras, tensorflow, and onnx/pytorch, a modular and tiny c++ library for running math code and a java based math library on top of the core c++ library. Also includes samediff: a pytorch/tensorflow like library for running deep learning using automatic differentiation.
alterschema - Convert between JSON Schema specification versions.
Draft.js - A React framework for building text editors.
tslint - :vertical_traffic_light: An extensible linter for the TypeScript language