Policy pushdown resync API

The policy pushdown resync API re-pushes down all the data access policies from Data Governance and Catalog into your source system. To do this, the API first marks all policies for that connection as requiring a resynchronization. The next time the sync job runs, it pushes down the latest policies for those entities from Data Governance and Catalog.

You must have the Governance Administrator Metadata Command Center role to run this API.

The policy pushdown resync API works with Databricks and Microsoft Fabric Data Lakehouse.

The policy pushdown resync API resynchronizes data filter policies without exposing data. The API works differently for each source system.

For Databricks, the policy pushdown resync API replaces the existing row filter function. If the row filter function is already applied to the data, then it is still be applied when Data Governance and Catalog replaces the function. There is no point when the table is without a row filter function.

For Microsoft Fabric Data Lakehouse, the policy pushdown resync API creates a new security function and attaches it as a filter predicate on the target table. If the correct data filter policy already exists, Data Governance and Catalog atomically updates the predicate in place. If a different data filter policy is attached, Data Governance and Catalog detaches the old one first and then creates the data filter policy. Data Governance and Cataloghandles concurrent creation conflicts gracefully by falling back to an alter if the data filter policy already exists.

The following table describes methods and endpoints for the policy pushdown resync API:

The base API URL differs for each POD. For more information, see Send requests.

To find the connection ID based on the name, you can use /api/v2/connection/name/<name>.

For more information, see Connections in the Administrator help.