Potential Causes

Hevo is unable to create a table in the Destination with Auto Mapping enabled. This can happen if you have data of a table with the same name already present in the Destination but its metadata is deleted.

One such scenario where this might happen is:

Suppose you are trying to create a new managed table with the name customers in your Databricks Destination through Hevo. You have an old unmanaged table with the name customers already existing in the database. As Databricks does not allow you to have two tables with the same name in the database, you drop the existing table from the Destination. However, since this is an unmanaged table, dropping the table only deletes its metadata, the data is still present.

Suggested Actions

To resolve this error, do one of the following:

• Remove the data related to the table from your Destination warehouse using DBFS REST API or the File system utility.

• Disable Auto Mapping and create a new Destination table with a different name. Read Mapping an Event Type to a new Destination table for steps to create a new Destination table.

Revision History