Fix typos in OpenMetadata documentation (#22899)

This commit is contained in:
Copilot 2025-08-12 17:27:40 +05:30 committed by GitHub
parent dc4c75ded4
commit 42bfd65a15
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
17 changed files with 20 additions and 20 deletions

View File

@ -1,5 +1,5 @@
## Adding a new resource to load tests
Add a new `*.py` file to `test_resources/tasks`. The naming does not matter, but we use the resource name as defined in Java, but seperated by `_` (e.g. `TestCaseResource` becomes `test_case_tasks.py`).
Add a new `*.py` file to `test_resources/tasks`. The naming does not matter, but we use the resource name as defined in Java, but separated by `_` (e.g. `TestCaseResource` becomes `test_case_tasks.py`).
In your newly created file, you'll need to import at minimum 1 package
```python

View File

@ -6,7 +6,7 @@
You can find the GitHub release [here](https://github.com/open-metadata/OpenMetadata/releases/tag/1.6.4-release).
- Fix: Powerbi test connection sucess with bad credentials.
- Fix: Powerbi test connection success with bad credentials.
- Fix: Remove description check for columnDescriptionStatus.
- Fix: Markdown editor fix.
- Fix: Postgres usage not terminating with bad connection.

View File

@ -6,7 +6,7 @@
You can find the GitHub release [here](https://github.com/open-metadata/OpenMetadata/releases/tag/1.6.4-release).
- Fix: Powerbi test connection sucess with bad credentials.
- Fix: Powerbi test connection success with bad credentials.
- Fix: Remove description check for columnDescriptionStatus.
- Fix: Markdown editor fix.
- Fix: Postgres usage not terminating with bad connection.

View File

@ -6,7 +6,7 @@
You can find the GitHub release [here](https://github.com/open-metadata/OpenMetadata/releases/tag/1.6.4-release).
- Fix: Powerbi test connection sucess with bad credentials.
- Fix: Powerbi test connection success with bad credentials.
- Fix: Remove description check for columnDescriptionStatus.
- Fix: Markdown editor fix.
- Fix: Postgres usage not terminating with bad connection.

View File

@ -44,7 +44,7 @@ Configure and schedule PinotDB metadata and profiler workflows from the OpenMeta
- **Username**: Specify the User to connect to PinotDB. It should have enough privileges to read all the metadata.
- **Password**: Password to connect to PinotDB.
- **Host and Port**: Enter the fully qualified hostname and port number for your PinotDB deployment in the Host and Port field. Unlike broker host, prefix http:// or https:// must be added to contoller host. For example, pinot broker host can be set to `localhost:8099` and pinot controller host can be set to `http://localhost:9000`.
- **Host and Port**: Enter the fully qualified hostname and port number for your PinotDB deployment in the Host and Port field. Unlike broker host, prefix http:// or https:// must be added to controller host. For example, pinot broker host can be set to `localhost:8099` and pinot controller host can be set to `http://localhost:9000`.
- **databaseName**: Optional name to give to the database in OpenMetadata. If left blank, we will use default as the database name.
- **databaseSchema**: databaseSchema of the data source. This is optional parameter, if you would like to restrict the metadata reading to a single databaseSchema. When left blank, OpenMetadata Ingestion attempts to scan all the databaseSchema.
- **caCertificate**: Provide the path to ssl ca file.

View File

@ -25,7 +25,7 @@ Configure and schedule Amundsen metadata and profiler workflows from the OpenMet
## Requirements
Before this, you must create the service you want to get metadata for.
You can learn how to do it by folowing the initial part of the Connector documentation for the service.
You can learn how to do it by following the initial part of the Connector documentation for the service.
You can find the connectors list [here](/connectors).
### Python Requirements

View File

@ -49,7 +49,7 @@ openmetadata:
secretRef: elasticsearch-secrets
secretKey: openmetadata-elasticsearch-password
database:
host: <DATABSE_SQL_ENDPOINT>
host: <DATABASE_SQL_ENDPOINT>
port: 3306
driverClass: com.mysql.cj.jdbc.Driver
dbScheme: mysql

View File

@ -13,9 +13,9 @@ slug: /main-concepts/metadata-standard/schemas/entity/services/connections/pipel
- **`host`** *(string)*: DBT cloud Access URL.
- **`discoveryAPI`** *(string)*: DBT cloud Metadata API URL.
- **`accountId`** *(string)*: ID of your DBT cloud account.
- **`jobIds`** *(array)*: List of IDs of your DBT cloud jobs seperated by comma `,`.
- **`jobIds`** *(array)*: List of IDs of your DBT cloud jobs separated by comma `,`.
- **Items** *(string)*
- **`projectIds`** *(array)*: List of IDs of your DBT cloud projects seperated by comma `,`.
- **`projectIds`** *(array)*: List of IDs of your DBT cloud projects separated by comma `,`.
- **Items** *(string)*
- **`numberOfRuns`** *(integer)*: Number of runs to fetch from DBT cloud. Default: `100`.
- **`token`** *(string)*: Generated Token to connect to DBTCloud.

View File

@ -44,7 +44,7 @@ Configure and schedule PinotDB metadata and profiler workflows from the OpenMeta
- **Username**: Specify the User to connect to PinotDB. It should have enough privileges to read all the metadata.
- **Password**: Password to connect to PinotDB.
- **Host and Port**: Enter the fully qualified hostname and port number for your PinotDB deployment in the Host and Port field. Unlike broker host, prefix http:// or https:// must be added to contoller host. For example, pinot broker host can be set to `localhost:8099` and pinot controller host can be set to `http://localhost:9000`.
- **Host and Port**: Enter the fully qualified hostname and port number for your PinotDB deployment in the Host and Port field. Unlike broker host, prefix http:// or https:// must be added to controller host. For example, pinot broker host can be set to `localhost:8099` and pinot controller host can be set to `http://localhost:9000`.
- **databaseName**: Optional name to give to the database in OpenMetadata. If left blank, we will use default as the database name.
- **databaseSchema**: databaseSchema of the data source. This is optional parameter, if you would like to restrict the metadata reading to a single databaseSchema. When left blank, OpenMetadata Ingestion attempts to scan all the databaseSchema.
- **caCertificate**: Provide the path to ssl ca file.

View File

@ -25,7 +25,7 @@ Configure and schedule Amundsen metadata and profiler workflows from the OpenMet
## Requirements
Before this, you must create the service you want to get metadata for.
You can learn how to do it by folowing the initial part of the Connector documentation for the service.
You can learn how to do it by following the initial part of the Connector documentation for the service.
You can find the connectors list [here](/connectors).
### Python Requirements

View File

@ -49,7 +49,7 @@ openmetadata:
secretRef: elasticsearch-secrets
secretKey: openmetadata-elasticsearch-password
database:
host: <DATABSE_SQL_ENDPOINT>
host: <DATABASE_SQL_ENDPOINT>
port: 3306
driverClass: com.mysql.cj.jdbc.Driver
dbScheme: mysql

View File

@ -14,9 +14,9 @@ slug: /main-concepts/metadata-standard/schemas/entity/services/connections/pipel
- **`host`** *(string, format: uri)*: DBT cloud Access URL.
- **`discoveryAPI`** *(string, format: uri)*: DBT cloud Metadata API URL.
- **`accountId`** *(string)*: ID of your DBT cloud account.
- **`jobIds`** *(array)*: List of IDs of your DBT cloud jobs seperated by comma `,`.
- **`jobIds`** *(array)*: List of IDs of your DBT cloud jobs separated by comma `,`.
- **Items** *(string)*
- **`projectIds`** *(array)*: List of IDs of your DBT cloud projects seperated by comma `,`.
- **`projectIds`** *(array)*: List of IDs of your DBT cloud projects separated by comma `,`.
- **Items** *(string)*
- **`token`** *(string, format: password)*: Generated Token to connect to DBTCloud.
## Definitions

View File

@ -44,7 +44,7 @@ Configure and schedule PinotDB metadata and profiler workflows from the OpenMeta
- **Username**: Specify the User to connect to PinotDB. It should have enough privileges to read all the metadata.
- **Password**: Password to connect to PinotDB.
- **Host and Port**: Enter the fully qualified hostname and port number for your PinotDB deployment in the Host and Port field. Unlike broker host, prefix http:// or https:// must be added to contoller host. For example, pinot broker host can be set to `localhost:8099` and pinot controller host can be set to `http://localhost:9000`.
- **Host and Port**: Enter the fully qualified hostname and port number for your PinotDB deployment in the Host and Port field. Unlike broker host, prefix http:// or https:// must be added to controller host. For example, pinot broker host can be set to `localhost:8099` and pinot controller host can be set to `http://localhost:9000`.
- **databaseName**: Optional name to give to the database in OpenMetadata. If left blank, we will use default as the database name.
- **databaseSchema**: databaseSchema of the data source. This is optional parameter, if you would like to restrict the metadata reading to a single databaseSchema. When left blank, OpenMetadata Ingestion attempts to scan all the databaseSchema.
- **caCertificate**: Provide the path to ssl ca file.

View File

@ -25,7 +25,7 @@ Configure and schedule Amundsen metadata and profiler workflows from the OpenMet
## Requirements
Before this, you must create the service you want to get metadata for.
You can learn how to do it by folowing the initial part of the Connector documentation for the service.
You can learn how to do it by following the initial part of the Connector documentation for the service.
You can find the connectors list [here](/connectors).
### Python Requirements

View File

@ -49,7 +49,7 @@ openmetadata:
secretRef: elasticsearch-secrets
secretKey: openmetadata-elasticsearch-password
database:
host: <DATABSE_SQL_ENDPOINT>
host: <DATABASE_SQL_ENDPOINT>
port: 3306
driverClass: com.mysql.cj.jdbc.Driver
dbScheme: mysql

View File

@ -14,9 +14,9 @@ slug: /main-concepts/metadata-standard/schemas/entity/services/connections/pipel
- **`host`** *(string, format: uri)*: DBT cloud Access URL.
- **`discoveryAPI`** *(string, format: uri)*: DBT cloud Metadata API URL.
- **`accountId`** *(string)*: ID of your DBT cloud account.
- **`jobIds`** *(array)*: List of IDs of your DBT cloud jobs seperated by comma `,`.
- **`jobIds`** *(array)*: List of IDs of your DBT cloud jobs separated by comma `,`.
- **Items** *(string)*
- **`projectIds`** *(array)*: List of IDs of your DBT cloud projects seperated by comma `,`.
- **`projectIds`** *(array)*: List of IDs of your DBT cloud projects separated by comma `,`.
- **Items** *(string)*
- **`token`** *(string, format: password)*: Generated Token to connect to DBTCloud.
## Definitions

View File

@ -37,7 +37,7 @@ $$
$$section
### Pinot Controller Host $(id="pinotControllerHost")
Pinot Controller Host and Port of the data source. Unlike broker host, prefix http:// or https:// must be added to contoller host. For example, you can set it to `http://localhost:9000`
Pinot Controller Host and Port of the data source. Unlike broker host, prefix http:// or https:// must be added to controller host. For example, you can set it to `http://localhost:9000`
$$
$$section