You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I am an SDV Enterprise user and my primary keys are of premium sdtypes (email, phone_number, ...), then SDV will assign the primary key column to a contextual anonymization transformer such as DomainBasedAnonymizer or AnonymizedGeoExtractor. Such transformers are not designed to keep uniqueness in mind, meaning that it may be possible that some primary keys repeat.
Solution
As a quick solution, we should ensure that we do not assign Contextual Anonymization transformers to primary keys. Instead, we should fall back on AnonymizedFaker like we do for public SDV.
(In the future, we can think about how Contextual Anonymization transformers can support uniqueness. We'd likely need to think through a different algorithm for each one.)
The text was updated successfully, but these errors were encountered:
Environment Details
Error Description
My metadata might list a semantic, PII type as a primary key -- for example an
email
.If I am an SDV Enterprise user and my primary keys are of premium sdtypes (
email
,phone_number
, ...), then SDV will assign the primary key column to a contextual anonymization transformer such as DomainBasedAnonymizer or AnonymizedGeoExtractor. Such transformers are not designed to keep uniqueness in mind, meaning that it may be possible that some primary keys repeat.Solution
As a quick solution, we should ensure that we do not assign Contextual Anonymization transformers to primary keys. Instead, we should fall back on AnonymizedFaker like we do for public SDV.
(In the future, we can think about how Contextual Anonymization transformers can support uniqueness. We'd likely need to think through a different algorithm for each one.)
The text was updated successfully, but these errors were encountered: