Schema Editor
Use the Schema Editor to view or edit the MongoDB collection schema that you want to import.
You can access the Schema Editor from the ODBC Data Source Administrator when you configure the Informatica MongoDB ODBC Driver DSN.
When you define a schema in the Informatica MongoDB ODBC driver DSN, you must specify a schema definition file. You can use an existing schema definition file or create a new one. After you specify a schema definition file, you can import the collections in the database to the schema definition file. You can import all the collections in the database or a particular collection. You can use a JSON filter to filter records on a collection. You can also export those collections that are missing in the schema definition file.
When you open the Schema Editor, all the databases and collections in the schema definition file appear. When you select a collection, the collection properties and document properties appear on the right pane. You can modify the properties and save the schema. You can also save the schema changes to a new schema definition file.
Collection Properties
Before you import a collection, you can view or edit the properties associated with the collection in the Schema Editor.
You can view or edit the following collection properties in the Schema Editor:
- ODBC Table Name
- The name of the collection to use for the schema. Default is the same as source table name. You can change this value to match the name that you require when you import the ODBC data source in Informatica Cloud.
- ODBC Catalog Name
- The name of the catalog that to use for the schema. Default is the same as source catalog name. You can change this value to match the name that you require when you import the ODBC data source in the Informatica Cloud.
- Source Table Name
- The name of the collection in the source database. You cannot change this value.
- Source Catalog Name
- The name of the source database. You cannot change this value.
- Virtual Type
- Indicates whether the collection is a virtual collection or not. Reserved for future use.
- Permissions
- The permissions assigned to you. Reserved for future use.
Document Properties
When you select a collection in the Schema Editor, you can view or change the column metadata of the collection.
The following fields are available in the column metadata:
- ODBC Column Name
- The name of the column that you want to use in the database schema. Default is the source column name. You can change this value to match the name that you require when you import the ODBC data source in Informatica Cloud..
- SQL Type
- The ODBC data type of the column. The Secure Agent uses the SQL type when you run the session that uses the ODBC data source. You can change the data type based on your requirement.
- Source Column Name
- The name of the column in the source database. You cannot change this value.
- Source Type
- The data type of the column in the source database. The Secure Agent uses the SQL type when you run the session that uses the ODBC data source. You can change the data type based on your requirement.
- Hide Column
- You can choose to hide the column so that it does not appear in the schema.
- Behavior
- The behavior field shows whether the column is scalar or a container. Scalar columns contain a single value like an integer or a string. Container columns have multiple values. Arrays and documents are examples of container columns.
Note: Container columns do not support transformations.
- Key Type
- The key type field shows whether the column is a key column.
- The following values are possible for the key type:
- - Primary key
- - Foriegn key
- - Not a key
- You cannot change the key type of a column.
- ODBC Type Hint
- The ODBC type hit field shows the possible ODBC data type of the column. You can choose the SQL type of a column based on the hint.
- Source Nesting Level
- The source nesting level field displays the level at which the column is nested in the document metadata. You can use the MongoDB ODBC driver to read up to five levels of nested columns and write up to three levels of nested columns.
- Alternate Source Type
- The alternate source type field displays the alternate data type of the column in the source database.