yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-12-05 03:54:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

update druid docs (#10735)

Browse Source
This commit is contained in:
NiharDoshi99 2023-03-23 22:16:14 +05:30 committed by GitHub
parent 48cc249b11
commit bfa0905093
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
openmetadata-docs/content/connectors/database/druid/airflow.md
View File

@ -72,7 +72,7 @@ source:
username: <username> username: <username>
password: <password> password: <password>
hostPort: <hostPort> hostPort: <hostPort>
database: <database> databaseName: default
sourceConfig: sourceConfig:
config: config:
type: DatabaseMetadata type: DatabaseMetadata
@ -117,7 +117,7 @@ workflowConfig:
- **username**: Specify the User to connect to Druid. It should have enough privileges to read all the metadata. - **username**: Specify the User to connect to Druid. It should have enough privileges to read all the metadata.
- **password**: Password to connect to Druid. - **password**: Password to connect to Druid.
- **hostPort**: Enter the fully qualified hostname and port number for your Druid deployment in the Host and Port field. - **hostPort**: Enter the fully qualified hostname and port number for your Druid deployment in the Host and Port field.
- **database**: The database of the data source is an optional parameter, if you would like to restrict the metadata reading to a single database. If left blank, OpenMetadata ingestion attempts to scan all the databases. - **Database Name**: Optional name to give to the database in OpenMetadata. If left blank, we will use default as the database name.
- **Connection Options (Optional)**: Enter the details for any additional connection options that can be sent to Druid during the connection. These details must be added as Key-Value pairs. - **Connection Options (Optional)**: Enter the details for any additional connection options that can be sent to Druid during the connection. These details must be added as Key-Value pairs.
- **Connection Arguments (Optional)**: Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Druid during the connection. These details must be added as Key-Value pairs. - **Connection Arguments (Optional)**: Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Druid during the connection. These details must be added as Key-Value pairs.
- In case you are using Single-Sign-On (SSO) for authentication, add the `authenticator` details in the Connection Arguments as a Key-Value pair as follows: `"authenticator" : "sso_login_url"` - In case you are using Single-Sign-On (SSO) for authentication, add the `authenticator` details in the Connection Arguments as a Key-Value pair as follows: `"authenticator" : "sso_login_url"`
@ -367,7 +367,7 @@ source:
username: "<username>" username: "<username>"
password: "<password>" password: "<password>"
hostPort: "<hostPort>" hostPort: "<hostPort>"
database: "<database>" databaseName: "default"
sourceConfig: sourceConfig:
config: config:
type: Profiler type: Profiler

6
openmetadata-docs/content/connectors/database/druid/cli.md
View File

@ -72,7 +72,7 @@ source:
username: <username> username: <username>
password: <password> password: <password>
hostPort: <hostPort> hostPort: <hostPort>
database: <database> databaseName: default
sourceConfig: sourceConfig:
config: config:
type: DatabaseMetadata type: DatabaseMetadata
@ -117,7 +117,7 @@ workflowConfig:
- **username**: Specify the User to connect to Druid. It should have enough privileges to read all the metadata. - **username**: Specify the User to connect to Druid. It should have enough privileges to read all the metadata.
- **password**: Password to connect to Druid. - **password**: Password to connect to Druid.
- **hostPort**: Enter the fully qualified hostname and port number for your Druid deployment in the Host and Port field. - **hostPort**: Enter the fully qualified hostname and port number for your Druid deployment in the Host and Port field.
- **database**: The database of the data source is an optional parameter, if you would like to restrict the metadata reading to a single database. If left blank, OpenMetadata ingestion attempts to scan all the databases. - **Database Name**: Optional name to give to the database in OpenMetadata. If left blank, we will use default as the database name.
- **Connection Options (Optional)**: Enter the details for any additional connection options that can be sent to Druid during the connection. These details must be added as Key-Value pairs. - **Connection Options (Optional)**: Enter the details for any additional connection options that can be sent to Druid during the connection. These details must be added as Key-Value pairs.
- **Connection Arguments (Optional)**: Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Druid during the connection. These details must be added as Key-Value pairs. - **Connection Arguments (Optional)**: Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Druid during the connection. These details must be added as Key-Value pairs.
- In case you are using Single-Sign-On (SSO) for authentication, add the `authenticator` details in the Connection Arguments as a Key-Value pair as follows: `"authenticator" : "sso_login_url"` - In case you are using Single-Sign-On (SSO) for authentication, add the `authenticator` details in the Connection Arguments as a Key-Value pair as follows: `"authenticator" : "sso_login_url"`
@ -319,7 +319,7 @@ source:
username: "<username>" username: "<username>"
password: "<password>" password: "<password>"
hostPort: "<hostPort>" hostPort: "<hostPort>"
database: "<database>" databaseName: default
sourceConfig: sourceConfig:
config: config:
type: Profiler type: Profiler

2
openmetadata-docs/content/connectors/database/druid/index.md
View File

@ -148,7 +148,7 @@ the changes.
- **Username**: Specify the User to connect to Druid. It should have enough privileges to read all the metadata. - **Username**: Specify the User to connect to Druid. It should have enough privileges to read all the metadata.
- **Password**: Password to connect to Druid. - **Password**: Password to connect to Druid.
- **Host and Port**: Enter the fully qualified hostname and port number for your Druid deployment in the Host and Port field. - **Host and Port**: Enter the fully qualified hostname and port number for your Druid deployment in the Host and Port field.
- **Database**: The database of the data source is an optional parameter, if you would like to restrict the metadata reading to a single database. If left blank, OpenMetadata ingestion attempts to scan all the databases. - **Database Name**: Optional name to give to the database in OpenMetadata. If left blank, we will use default as the database name.
- **Connection Options (Optional)**: Enter the details for any additional connection options that can be sent to Druid during the connection. These details must be added as Key-Value pairs. - **Connection Options (Optional)**: Enter the details for any additional connection options that can be sent to Druid during the connection. These details must be added as Key-Value pairs.
- **Connection Arguments (Optional)**: Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Druid during the connection. These details must be added as Key-Value pairs. - **Connection Arguments (Optional)**: Enter the details for any additional connection arguments such as security or protocol configs that can be sent to Druid during the connection. These details must be added as Key-Value pairs.
- In case you are using Single-Sign-On (SSO) for authentication, add the `authenticator` details in the Connection Arguments as a Key-Value pair as follows: `"authenticator" : "sso_login_url"` - In case you are using Single-Sign-On (SSO) for authentication, add the `authenticator` details in the Connection Arguments as a Key-Value pair as follows: `"authenticator" : "sso_login_url"`