Set of fields to compute k-anonymity over. When multiple fields are specified, they are considered a single composite key. Structs and repeated data types are not supported; however, nested fields are supported so long as they are not structs themselves or nested within a repeated field.
Message indicating that multiple rows might be associated to a single individual. If the same entity_id is associated to multiple quasi-identifier tuples over distinct rows, we consider the entire collection of tuples as the composite quasi-identifier. This collection is a multiset: the order in which the different tuples appear in the dataset is ignored, but their frequency is taken into account. Important note: a maximum of 1000 rows can be associated to a single entity ID. If more rows are associated with the same entity ID, some might be ignored.
getQuasiIds
Set of fields to compute k-anonymity over. When multiple fields are
specified, they are considered a single composite key. Structs and
repeated data types are not supported; however, nested fields are
supported so long as they are not structs themselves or nested within
a repeated field.
Set of fields to compute k-anonymity over. When multiple fields are
specified, they are considered a single composite key. Structs and
repeated data types are not supported; however, nested fields are
supported so long as they are not structs themselves or nested within
a repeated field.
Message indicating that multiple rows might be associated to a
single individual. If the same entity_id is associated to multiple
quasi-identifier tuples over distinct rows, we consider the entire
collection of tuples as the composite quasi-identifier. This collection
is a multiset: the order in which the different tuples appear in the
dataset is ignored, but their frequency is taken into account.
Important note: a maximum of 1000 rows can be associated to a single
entity ID. If more rows are associated with the same entity ID, some
might be ignored.
Message indicating that multiple rows might be associated to a
single individual. If the same entity_id is associated to multiple
quasi-identifier tuples over distinct rows, we consider the entire
collection of tuples as the composite quasi-identifier. This collection
is a multiset: the order in which the different tuples appear in the
dataset is ignored, but their frequency is taken into account.
Important note: a maximum of 1000 rows can be associated to a single
entity ID. If more rows are associated with the same entity ID, some
might be ignored.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Data Loss Prevention V2 Client - Class KAnonymityConfig (2.6.1)\n\nVersion latestkeyboard_arrow_down\n\n- [2.6.1 (latest)](/php/docs/reference/cloud-dlp/latest/V2.PrivacyMetric.KAnonymityConfig)\n- [2.6.0](/php/docs/reference/cloud-dlp/2.6.0/V2.PrivacyMetric.KAnonymityConfig)\n- [2.4.1](/php/docs/reference/cloud-dlp/2.4.1/V2.PrivacyMetric.KAnonymityConfig)\n- [2.3.0](/php/docs/reference/cloud-dlp/2.3.0/V2.PrivacyMetric.KAnonymityConfig)\n- [2.2.3](/php/docs/reference/cloud-dlp/2.2.3/V2.PrivacyMetric.KAnonymityConfig)\n- [2.1.0](/php/docs/reference/cloud-dlp/2.1.0/V2.PrivacyMetric.KAnonymityConfig)\n- [2.0.0](/php/docs/reference/cloud-dlp/2.0.0/V2.PrivacyMetric.KAnonymityConfig)\n- [1.19.0](/php/docs/reference/cloud-dlp/1.19.0/V2.PrivacyMetric.KAnonymityConfig)\n- [1.18.0](/php/docs/reference/cloud-dlp/1.18.0/V2.PrivacyMetric.KAnonymityConfig)\n- [1.17.0](/php/docs/reference/cloud-dlp/1.17.0/V2.PrivacyMetric.KAnonymityConfig)\n- [1.16.0](/php/docs/reference/cloud-dlp/1.16.0/V2.PrivacyMetric.KAnonymityConfig)\n- [1.15.1](/php/docs/reference/cloud-dlp/1.15.1/V2.PrivacyMetric.KAnonymityConfig)\n- [1.14.0](/php/docs/reference/cloud-dlp/1.14.0/V2.PrivacyMetric.KAnonymityConfig)\n- [1.13.2](/php/docs/reference/cloud-dlp/1.13.2/V2.PrivacyMetric.KAnonymityConfig)\n- [1.12.0](/php/docs/reference/cloud-dlp/1.12.0/V2.PrivacyMetric.KAnonymityConfig)\n- [1.11.0](/php/docs/reference/cloud-dlp/1.11.0/V2.PrivacyMetric.KAnonymityConfig)\n- [1.10.2](/php/docs/reference/cloud-dlp/1.10.2/V2.PrivacyMetric.KAnonymityConfig)\n- [1.9.0](/php/docs/reference/cloud-dlp/1.9.0/V2.PrivacyMetric.KAnonymityConfig)\n- [1.8.6](/php/docs/reference/cloud-dlp/1.8.6/V2.PrivacyMetric.KAnonymityConfig) \nReference documentation and code samples for the Data Loss Prevention V2 Client class KAnonymityConfig.\n\nk-anonymity metric, used for analysis of reidentification risk.\n\nGenerated from protobuf message `google.privacy.dlp.v2.PrivacyMetric.KAnonymityConfig`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Dlp \\\\ V2 \\\\ PrivacyMetric\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getQuasiIds\n\nSet of fields to compute k-anonymity over. When multiple fields are\nspecified, they are considered a single composite key. Structs and\nrepeated data types are not supported; however, nested fields are\nsupported so long as they are not structs themselves or nested within\na repeated field.\n\n### setQuasiIds\n\nSet of fields to compute k-anonymity over. When multiple fields are\nspecified, they are considered a single composite key. Structs and\nrepeated data types are not supported; however, nested fields are\nsupported so long as they are not structs themselves or nested within\na repeated field.\n\n### getEntityId\n\nMessage indicating that multiple rows might be associated to a\nsingle individual. If the same entity_id is associated to multiple\nquasi-identifier tuples over distinct rows, we consider the entire\ncollection of tuples as the composite quasi-identifier. This collection\nis a multiset: the order in which the different tuples appear in the\ndataset is ignored, but their frequency is taken into account.\n\nImportant note: a maximum of 1000 rows can be associated to a single\nentity ID. If more rows are associated with the same entity ID, some\nmight be ignored.\n\n### hasEntityId\n\n### clearEntityId\n\n### setEntityId\n\nMessage indicating that multiple rows might be associated to a\nsingle individual. If the same entity_id is associated to multiple\nquasi-identifier tuples over distinct rows, we consider the entire\ncollection of tuples as the composite quasi-identifier. This collection\nis a multiset: the order in which the different tuples appear in the\ndataset is ignored, but their frequency is taken into account.\n\nImportant note: a maximum of 1000 rows can be associated to a single\nentity ID. If more rows are associated with the same entity ID, some\nmight be ignored."]]
