mirror of
https://github.com/open-metadata/OpenMetadata.git
synced 2025-11-25 07:04:43 +00:00
Docs - Add schemas navigation info (#6494)
Docs - Add schemas navigation info (#6494)
This commit is contained in:
parent
6175b821c5
commit
0c7e4f716e
@ -66,6 +66,15 @@ You can modify any configuration and deploy by passing your own `values.yaml`.
|
|||||||
|
|
||||||
</Note>
|
</Note>
|
||||||
|
|
||||||
|
<Tip>
|
||||||
|
|
||||||
|
Make sure that, when using your own `values.yaml`, you are not overwriting elements such as the `image` of the containers.
|
||||||
|
This would prevent your new deployment to use the latest containers when running the upgrade.
|
||||||
|
|
||||||
|
If you are running into any issues, double-check what are the default values of the helm revision.
|
||||||
|
|
||||||
|
</Tip>
|
||||||
|
|
||||||
## Upgrade OpenMetdata
|
## Upgrade OpenMetdata
|
||||||
|
|
||||||
We upgrade OpenMetadata with the below command:
|
We upgrade OpenMetadata with the below command:
|
||||||
|
|||||||
@ -4,3 +4,21 @@ slug: /main-concepts/metadata-standard/schemas
|
|||||||
---
|
---
|
||||||
|
|
||||||
# Schemas
|
# Schemas
|
||||||
|
|
||||||
|
The OpenMetadata standard is powered by [JSON Schemas](https://json-schema.org/), as a readable and language-agnostic
|
||||||
|
solution that allows us to automatically generate code for the different pieces of the project.
|
||||||
|
|
||||||
|
<Note>
|
||||||
|
|
||||||
|
Curious about how OpenMetadata is built? You can take a look at the [High Level Design](/main-concepts/high-level-design).
|
||||||
|
|
||||||
|
</Note>
|
||||||
|
|
||||||
|
You can explore the JSON Schemas in different ways:
|
||||||
|
1. You can check all the definitions in [GitHub](https://github.com/open-metadata/OpenMetadata/tree/main/catalog-rest-service/src/main/resources/json/schema).
|
||||||
|
Navigating through the directories you can find, for example, the definition of a [Table](https://github.com/open-metadata/OpenMetadata/blob/main/catalog-rest-service/src/main/resources/json/schema/entity/data/table.json).
|
||||||
|
2. If you prefer to stay in the docs, we also have you covered. We have converted the JSON Schemas to markdown files
|
||||||
|
that you can explore following the left menu titles, or navigating the structure by clicking on `Next` at the
|
||||||
|
end of each page. Again, this would be the structure of a [Table](/main-concepts/metadata-standard/schemas/entity/data/table).
|
||||||
|
In this generation we wanted to maintain the same structure as the GitHub repository. Any empty file means that you reached
|
||||||
|
a directory, but you can keep exploring until finding the right Entity, or you can also look for it using the Search Bar.
|
||||||
|
|||||||
@ -1,8 +0,0 @@
|
|||||||
---
|
|
||||||
title: index
|
|
||||||
slug: /main-concepts/metadata-standard/schemas
|
|
||||||
---
|
|
||||||
|
|
||||||
# schema
|
|
||||||
|
|
||||||
Documentation file automatically generated at 2022-07-14 10:51:34.749986.
|
|
||||||
Loading…
x
Reference in New Issue
Block a user