[Docs] - host.docker.internal docs & postgres ingestAllDatabases below db input (#12744)

This commit is contained in:
Pere Miquel Brull 2023-08-04 08:35:33 +02:00 committed by GitHub
parent cda004e35e
commit ac06f55bd0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
22 changed files with 29 additions and 30 deletions

View File

@ -63,6 +63,12 @@
"description": "Database of the data source. This is optional parameter, if you would like to restrict the metadata reading to a single database. When left blank, OpenMetadata Ingestion attempts to scan all the databases.",
"type": "string"
},
"ingestAllDatabases": {
"title": "Ingest All Databases",
"description": "Ingest data from all databases in Postgres. You can use databaseFilterPattern on top of this.",
"type": "boolean",
"default": false
},
"sslMode": {
"title": "SSL Mode",
"description": "SSL Mode to connect to postgres database.",
@ -85,12 +91,6 @@
"type": "string",
"default": "PostgresPolicyTags"
},
"ingestAllDatabases": {
"title": "Ingest All Databases",
"description": "Ingest data from all databases in Postgres. You can use databaseFilterPattern on top of this.",
"type": "boolean",
"default": false
},
"connectionOptions": {
"title": "Connection Options",
"$ref": "../connectionBasicType.json#/definitions/connectionOptions"

View File

@ -43,7 +43,7 @@ $$section
This parameter specifies the host and port of the AzureSQL instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `azure-sql-service-name.database.windows.net:1433`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:3000` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:3000` as the value.
$$
$$section

View File

@ -58,7 +58,7 @@ $$section
This parameter specifies the host and port of the ClickHouse instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:3000`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:3000` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:3000` as the value.
$$
$$section

View File

@ -29,7 +29,7 @@ $$section
### Host Port $(id="hostPort")
This parameter specifies the host and port of the Databricks instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `adb-xyz.azuredatabricks.net:443`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:3000` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:3000` as the value.
$$
$$section

View File

@ -58,7 +58,7 @@ $$section
This parameter specifies the host and port of the Db2 instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:8000`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:8000` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:8000` as the value.
$$
$$section

View File

@ -31,7 +31,7 @@ $$section
This parameter specifies the host and port of the Druid instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:8000`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:8000` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:8000` as the value.
$$
$$section

View File

@ -24,7 +24,7 @@ Password to connect to Hive.
This parameter specifies the host and port of the Hive instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `myhivehost:10000`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:10000` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:10000` as the value.
### Auth
The auth parameter specifies the authentication method to use when connecting to the Hive server. Possible values are `LDAP`, `NONE`, `CUSTOM`, or `KERBEROS`. If you are using Kerberos authentication, you should set auth to `KERBEROS`. If you are using custom authentication, you should set auth to `CUSTOM` and provide additional options in the `authOptions` parameter.
@ -146,7 +146,7 @@ Find more information about [Source Identity](https://docs.aws.amazon.com/STS/la
This parameter specifies the host and port of the Postgres instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:5432`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:5432` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:5432` as the value.
### Database
@ -275,7 +275,7 @@ Find more information about [Source Identity](https://docs.aws.amazon.com/STS/la
This parameter specifies the host and port of the MySQL instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:3306`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:3306` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:3306` as the value.
### Database Name $(id="databaseName")
In OpenMetadata, the Database Service hierarchy works as follows:

View File

@ -32,7 +32,7 @@ $$section
This parameter specifies the host and port of the Impala instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `myimpalahost:21050`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:21050` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:21050` as the value.
$$
$$section

View File

@ -47,7 +47,7 @@ $$section
This parameter specifies the host and port of the MariaDB instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:3306`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:3306` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:3306` as the value.
$$
$$section

View File

@ -35,7 +35,7 @@ $$section
This parameter specifies the host and port of the MongoDB instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:27017`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:27017` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:27017` as the value.
$$
$$section

View File

@ -78,7 +78,7 @@ $$section
This parameter specifies the host and port of the MSSQL instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:1433`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:1433` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:1433` as the value.
$$
$$section

View File

@ -155,7 +155,7 @@ $$section
This parameter specifies the host and port of the MySQL instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:3306`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:3306` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:3306` as the value.
$$
$$section

View File

@ -63,7 +63,7 @@ $$section
This parameter specifies the host and port of the Oracle instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:1521`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:1521` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:1521` as the value.
$$
$$section

View File

@ -31,7 +31,7 @@ $$section
This parameter specifies the host and port of the PinotDB instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:8099`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:8099` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:8099` as the value.
$$
$$section

View File

@ -156,7 +156,7 @@ $$section
This parameter specifies the host and port of the Postgres instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:5432`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:5432` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:5432` as the value.
$$
$$section

View File

@ -34,7 +34,7 @@ $$section
This parameter specifies the host and port of the Presto instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:8080`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:8080` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:8080` as the value.
$$
$$section

View File

@ -45,7 +45,7 @@ $$section
### Host Port $(id="hostPort")
This parameter specifies the host and port of the Redshift instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:5439`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:5439` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:5439` as the value.
$$
$$section

View File

@ -30,7 +30,7 @@ $$section
### Host Port $(id="hostPort")
This parameter specifies the host and port of the SQLite instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:3306`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:3306` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:3306` as the value.
Keep it blank for in-memory databases.
$$

View File

@ -47,7 +47,7 @@ $$section
This parameter specifies the host and port of the SAP Hana instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:39041`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:39041` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:39041` as the value.
$$
$$section

View File

@ -45,7 +45,7 @@ $$section
### Host Port $(id="hostPort")
This parameter specifies the host and port of the SingleStore instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:3306`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:3306` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:3306` as the value.
$$
$$section

View File

@ -38,7 +38,7 @@ $$section
### Host Port $(id="hostPort")
This parameter specifies the host and port of the Trino instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:8080`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:8080` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:8080` as the value.
$$
$$section

View File

@ -72,8 +72,7 @@ $$section
This parameter specifies the host and port of the Vertica instance. This should be specified as a string in the format `hostname:port`. For example, you might set the hostPort parameter to `localhost:5433`.
If your database service and Open Metadata are both running via docker locally, use `host.docker.internal:5433` as the value.
If you are running the OpenMetadata ingestion in a docker and your services are hosted on the `localhost`, then use `host.docker.internal:5433` as the value.
$$
$$section