Skip to main content Skip to complementary content

Clearing the data warehouse metadata cache

To improve performance when reading from the Landing Zone or from the Data Warehouse tables, Compose caches the metadata from both the Landing Zone and the Data Warehouse tables. However, synchronization issues may sometimes occur if the metadata structure of the Landing Zone or the Data Warehouse tables is altered outside of the Compose project.

If you aware of external changes to the metadata or if you notice any data synchronization anomalies, Compose enables you to clear the metadata cache, either using the UI or using the CLI.

Clearing the data warehouse metadata cache with the web console

  1. In the Data Warehouse panel, select Clear Metadata Cache from the menu in the top right corner.

    A progress window opens.

  2. After the metadata cache has been cleared, click Close to exit the progress window.

For information on clearing the Landing Zone metadata cache, see Clearing the Landing Zone metadata cache.

Clearing the metadata cache with the CLI

Information note

The storage value for the --type parameter described below refers to the data warehouse metadata cache.

You can also clear the metadata cache using the CLI.

Command syntax:

ComposeCli.exe clear_cache --project project_name [--type landing|storage] [--landing_zone source_name]

Parameters

Parameter Description
--project The name of the project.
--type

Which type of metadata cache to clear. Possible values are:

  • landing

  • storage

     

    If --type landing and you want to clear a specific landing zone, you must set the --landing_zone parameter as well. To clear the metadata cache in all landing zones, specify --type landing and omit the --landing_zone parameter.

--landing_zone the name of the landing zone when --type landing_zone

Example

ComposeCli.exe clear_cache --project MyProject --type landing --landing_zone MySource1

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!