Metadata import connectors
You define a data connector when you import data assets by using a connector and reading data from a source system, such as a database or file storage system. A connector is a reusable connection between a data source, such as a database, data file folder, or data file. After you create a data connection in Watson Knowledge Catalog and use it to share data to the metadata repository, it is stored and available for other users to use.
Data connector identity
The identity of a data connection can have the following components:
- Name of the data connection (required)
- Connection string
The connection string differs depending on the type of connection that you are using. The following table shows the connection string for each type of connector:
Table 1. Connection strings for each type of connector and bridge
Connector or bridge | Connection string |
---|---|
Amazon S3 connector | Region |
File connector - HDFS | Host |
File connector - Engine tier | Not used |
Greenplum connector | Data source |
IBM Db2 connector | Database |
JDBC connector | URL to data source |
ODBC connector | Data source |
Oracle connector | Server |
Teradata connector | Server |
Netezza connector | Data source |
Rules for creating and editing data connections
In Watson Knowledge Catalog, creating and editing data connections is tied to the import process and to the import area. You create or edit data connections while in the import wizard. Your ability to edit the data connection in a particular import area depends on whether you have shared an import from that area to the metadata repository.
When no import has been shared to the metadata repository from the import area that you are working in, you can select an existing data connection or create a new data connection. You can edit any of the properties of the data connection, even after running imports, as long as you do not share an import to the metadata repository.
After an import has been shared to the metadata repository from the import area that you are working in, you can change only the password of the data connection while working in that import area. However, you can select and edit the data connection if you create a new import area. If you change the identity of a data connection by editing the name or connection string of a data connection, a new data connection is created after your import area is shared to the metadata repository. If you create a data connection that has the same identity properties as an existing data connection, when the import is shared to the metadata repository your new data connection overwrites the existing data connection.
If you edit the description or password of a data connection or the user name, the changed information is saved in the staging area. Because the description, password, and user name are not part of the identity of the data connection, when you share the staged import to the metadata repository, the changes are merged into the existing data connection.
When you create or edit a data connection you must save the password if you want to be able to use Discovery and classify the imported data asset. By default, you can save the required password or security when you create or edit a data connection.
Supported connectors
The following connectors are supported for importing metadata by using Watson Knowledge Catalog.
Table 2. Supported connectors and metadata parameters
Connectors | Imported metadata parameters |
---|---|
Amazon S3 connector | Amazon S3 buckets, data file folders, data file definitions, data file definitions structures, data files, data file structures |
File connector - Engine tier | Data file folders, data files, and data file structures from the file system on the engine tier computer. |
File connector - HDFS | Data file folders, data files, and data file structures from Hadoop Distributed File System (HDFS) |
Greenplum connector | Implemented data resources such as database tables and schemas |
Hive connector | Implemented data resources such as database tables and schemas |
IBM Cognos TM 1 | Cubes, dimensions, views, and other objects from Cognos TM1, Version 10.2, Fix Pack 1 and later. Views are imported as BI reports. |
IBM DB2 connector | Implemented data resources such as database tables and schemas |
IBM Netezza connector | Implemented data resources such as database tables and schemas |
JDBC connector | Implemented data resources such as database tables and schemas |
ODBC connector | Implemented data resources such as database tables and schemas |
Oracle connector 11g | Implemented data resources such as database tables and schemas |
Teradata connector | Implemented data resources such as database tables and schemas |
Learn more
Parent topic: Metadata asset types