Skip to main content
 print this page

Update an existing Lake Formation data filter

PUT 

/datasets/:id/data-permissions/:dfname

Replaces AuthorizedTags (EffectiveTags) and updates Columns/Rows on an existing Lake Formation data filter identified by path dfname, then starts the async grant/revoke workflow.

Required request body fields (IPV-1055 if any missing): AuthorizedTags (array), Columns (object), Rows (object). Types must be list/dict/dict respectively (IPV-1060). Columns and Rows must each include Condition and Expression. Encoding is optional (defaults to none) and applies to Rows.Expression.

Expected Condition values (same contract as create): Columns.Condition = include | exclude | all; Rows.Condition = custom | all. When Columns.Condition is all, Expression is ignored and the full dataset schema is used. Rows.Expression must be non-empty; use Encoding=base64 when the expression is base64-encoded (IPV-1045 / GE-1034 on bad Encoding or empty expression).

Unlike create, update does not pre-check Condition enums or that column names exist in DatasetSchema; invalid values may surface later as DS-1079 from Lake Formation. Caller must be owner or editor. Not supported for TBAC-enabled datasets (GE-1034). dfname must be the existing filter SystemName / Lake Formation Name for this dataset (typically {Domain}{DatasetName}{shortName}).

Request

Responses

Filter metadata/LF filter updated and async update workflow started. Message is "Data Permission update process started".

Response Headers
    Access-Control-Allow-Origin
    Access-Control-Allow-Methods
    Access-Control-Allow-Headers