The CSV file is only read when an explicit reconfigure operation is
triggered. If the file is changed, a configure operation (using
tpm update) must be initiated to force reconfiguration.
The CSV consists of multiple lines, one line for each rename
specification. Comments are supposed using the
Processing of the individual rules is executed in a specific order to
allow for complex matching and application of the rename changes.
220.127.116.11. Rename Filter Examples
When processing multiple entries that would match the same definition,
the above ordering rules are applied. For example, the definition:
europe.shanghai, while renaming
all other tables in the schema
asia to the schema
america. This is because the
schema.table rule is
matched first and then executed.
Complex renames involving multiple schemas, tables and columns can be
achieved by writing multiple rules into the same CSV file. For example
given a schema where all the tables currently reside in a single schema,
but must be renamed to specific continents, or to a 'miscellaneous'
schema, while also updating the column names to be more neutral would
require a detailed rename definition.
Existing tables are in the schema
Need to be renamed to:
Meanwhile, the table definition needs to be updated to support more
The area is being updated to contain the region within the country,
while the value should be renamed to the three-letter currency code, for
london table would
value column to
The definition can be divided up into simple definitions at each object
level, relying on the processing order to handle the individual
exceptions. Starting with the table renames for the continents:
A single rule to handle the renaming of any table not explicitly
mentioned in the list above into the
Now a rule to change the
column for all tables to
This requires a wildcard match against the schema and table names:
And finally the explicit changes for the value column to the