Resolve a schema refresh conflict for a renamed column

If you refresh a schema where the data source contains a column that has been renamed, the ingestion process will detect a conflict. In the following example, the ingested schema contains a column age, and in the updated schema, the column name has become current_age.

To resolve a refresh conflict due to a column rename, follow these steps:

1. Look up the new column with the search function or as follows:
   1. In the main menu, click , then Catalog.
      The Catalog Home opens.
   2. In the submenu, click Data Sources.
   3. Optionally, add the Refresh Conflict column to the table.
   4. In the table, expand the relevant schema and table to find the columns with refresh conflicts.
      
2. Select the updated column name and click Delete above the table.
   If necessary, select all column assets that are removed from the data source.
   
3. Click Yes to confirm the deletion of the column asset(s).
4. Click the name of the original column name.
   The column asset page appears.
5. In the resource toolbar, click Actions > Edit.
   The Edit <asset name> dialog box appears.
6. Change the name to the new ingested name.
   
7. Click Save.
8. Refresh the page.
   
9. Leave the column asset page open.
10. In the Refresh Conflict section of the column asset page, hover over the message and click on the right-hand side.
    
11. Click Yes to confirm the deletion of the attribute.
12. Click the browser's Back button to return to the Data Sources view of the schema.
    You can also click on the breadcrumb, as shown in the following image, to open the table asset page of the ingested schema.
    
    
13. If necessary, repeat steps 4 to 12 for other renamed column assets.
    

What's next?

You can now safely refresh the schema with the new data source; however, keep in mind this may take some time.