Before you migrate, consider the following rules and guidelines:
Parameterization
In advanced mode, you cannot use the parameter file from the mapping task to override the runtime parameters.
In mappings, when you parameterize the source and target object and select the Hive object from the mapping task and also override the schema and table, the agent ignores the overridden values.
Using multiple source objects
All the source objects used in a mappingmust be from the same database. You can override only the schema name but not the table name.
Dynamically refresh the data object schema
You cannot dynamically refresh the data object schema at runtime. You must maintain the same metadata for the table selected in the source, target, or lookup transformations and the corresponding advanced field overrides, as schema change handling is not applicable.
Overriding properties at runtime
Consider the following restrictions when you plan to override a property at runtime:
To configure an override, the design time and the overridden object table metadata must be the same.
When you specify an override to the schema or table, and the mapping contains a pre-SQL, post-SQL, and an SQL override, the mapping fails to pick the overridden table and instead uses the schema from the design time.
If you specify the pre-SQL, post-SQL, and SQL override without providing the schema or table name, the agent considers the schema and table name imported during the design time based on the database value specified in the connection string. If the database name is not provided in the connection, the mapping uses the default database in the Hive backend.
You cannot configure both an advanced filter in the Source transformation and a schema and table override in the advanced source properties. If both these properties are configured, then the only option is to update the filter condition in the mapping with the overridden table name and then run the mapping.
In advanced mode, if you specify the database name in the JDBC URL in the Hive connection properties and you also configure an override to the table and schema name in the advanced properties in the mapping, the database name in the connection URL is considered.