Warning We have announced the end of life of Jobserver and all related Jobserver integrations for September 30, 2024, with the exception of Public Sector customers using GovCloud or on-prem environments.
For information on registering a data source via Edge, go to Registering and synchronizing a data source via Edge.

Resolve a schema refresh conflict for a renamed table

If you refresh a schema where the data source contains a table that has been renamed, the ingestion process detects a conflict.

In the following example, the ingested schema contains a table that has been renamed.

Important 

In Collibra 2024.02, we've launched a new user interface (UI) in beta for Collibra Data Intelligence Platform! You can learn more about this latest UI in the UI overview.

Use the following options to see the documentation in the latest UI or in the previous, classic UI:

You have to manually resolve the conflicts before you continue. It is not possible to refresh a schema when there are conflicts.

Note You have to add the Refresh Conflict column to the table if it is not there already.

Steps

  1. On the main toolbar, click Products icon, and then click Catalog.
    The Catalog Home opens.
    The Catalog Home appears
  2. In the submenu, click Data Sources.
  3. Expand the tables to see all the columns that are contained in them.
  4. Delete the renamed table and its columns:
    1. Select the renamed table and all its contained columns.
    2. Above the table, click Delete.

    3. Click YesDelete to confirm the deletion of the column asset(s).
  5. Delete the Refresh Conflict attribute of the renamed table:
    1. Double click the Refresh Conflict attribute of the renamed table.
    2. In the Update Attribute dialog box, click .
    3. Click Save.
  6. Rename the renamed table:
    1. Double click the name of the renamed table.
    2. Type the new name of the table.
    3. Press the Enter key.
  7. Rename the columns of the renamed table:
    1. Click the names of the original columns.
      The column asset page appears.
    2. Click Actions > Edit.
    3. Change the name to the new ingested name.

    4. Click Save.
  8. Hover over the original table, in this example, firsttable, and click to the right of the table name.
  9. Change the name to the new ingested table name, in this example, firsttable2, and click to apply the change.

  10. Hover over a column contained in the table you just renamed and click to the right of the column name.
  11. Rename the column by replacing the table part of the name with that of the renamed table and click to apply the change.
    The column name is a concatenation of the table name and the original column name and so you just have to replace the table part of the name with the new table name. For example, to rename the column name firsttable > column1 to firsttable2 > column1, you just have to change firsttable to firsttable2 so that the column name becomes firsttable2 > column1.
  12. Repeat this action for all the columns in the renamed table.
    Now, you only see the new ingested table, firsttable2, and the columns contained in the table.

  13. Click the name of the renamed table.
    The table asset page appears.
  14. In the Refresh Conflict section, hover over the refresh conflict message and click on the right-hand side.

  15. Click Yes to confirm the deletion of the Refresh Conflict attribute.

What's next?

You can now safely refresh the schema with the data source.