Details about the container where the content being inspected is from.
↳ file_offset
int|string
Offset in bytes of the line, from the beginning of the file, where the finding is located. Populate if the item being scanned is only part of a bigger item, such as a shard of a file and you want to track the absolute position of the finding.
↳ row_offset
int|string
Offset of the row for tables. Populate if the row(s) being scanned are part of a bigger dataset and you want to keep track of their absolute position.
If the container is a table, additional information to make findings meaningful such as the columns that are primary keys. If not known ahead of time, can also be set within each inspect hybrid call and the two will be merged. Note that identifying_fields will only be stored to BigQuery, and only if the BigQuery action has been included.
Labels to represent user provided metadata about the data being inspected. If configured by the job, some key values may be required. The labels associated withFinding's produced by hybrid inspection. Label keys must be between 1 and 63 characters long and must conform to the following regular expression:[a-z]([-a-z0-9]*[a-z0-9])?. Label values must be between 0 and 63 characters long and must conform to the regular expression([a-z]([-a-z0-9]*[a-z0-9])?)?. No more than 10 labels can be associated with a given finding. Examples: * *"environment" : "production"* *"pipeline" : "etl"
getContainerDetails
Details about the container where the content being inspected is from.
Offset in bytes of the line, from the beginning of the file, where the
finding is located. Populate if the item being scanned is only part of a
bigger item, such as a shard of a file and you want to track the absolute
position of the finding.
Returns
Type
Description
int|string
setFileOffset
Offset in bytes of the line, from the beginning of the file, where the
finding is located. Populate if the item being scanned is only part of a
bigger item, such as a shard of a file and you want to track the absolute
position of the finding.
Parameter
Name
Description
var
int|string
Returns
Type
Description
$this
getRowOffset
Offset of the row for tables. Populate if the row(s) being scanned are
part of a bigger dataset and you want to keep track of their absolute
position.
Returns
Type
Description
int|string
setRowOffset
Offset of the row for tables. Populate if the row(s) being scanned are
part of a bigger dataset and you want to keep track of their absolute
position.
Parameter
Name
Description
var
int|string
Returns
Type
Description
$this
getTableOptions
If the container is a table, additional information to make findings
meaningful such as the columns that are primary keys. If not known ahead
of time, can also be set within each inspect hybrid call and the two
will be merged. Note that identifying_fields will only be stored to
BigQuery, and only if the BigQuery action has been included.
If the container is a table, additional information to make findings
meaningful such as the columns that are primary keys. If not known ahead
of time, can also be set within each inspect hybrid call and the two
will be merged. Note that identifying_fields will only be stored to
BigQuery, and only if the BigQuery action has been included.
Labels to represent user provided metadata about the data being inspected.
If configured by the job, some key values may be required.
The labels associated withFinding's produced by hybrid
inspection.
Label keys must be between 1 and 63 characters long and must conform
to the following regular expression:[a-z]([-a-z0-9]*[a-z0-9])?.
Label values must be between 0 and 63 characters long and must conform
to the regular expression([a-z]([-a-z0-9]*[a-z0-9])?)?.
No more than 10 labels can be associated with a given finding.
Examples:
Labels to represent user provided metadata about the data being inspected.
If configured by the job, some key values may be required.
The labels associated withFinding's produced by hybrid
inspection.
Label keys must be between 1 and 63 characters long and must conform
to the following regular expression:[a-z]([-a-z0-9]*[a-z0-9])?.
Label values must be between 0 and 63 characters long and must conform
to the regular expression([a-z]([-a-z0-9]*[a-z0-9])?)?.
No more than 10 labels can be associated with a given finding.
Examples:
[[["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 HybridFindingDetails (2.6.1)\n\nVersion latestkeyboard_arrow_down\n\n- [2.6.1 (latest)](/php/docs/reference/cloud-dlp/latest/V2.HybridFindingDetails)\n- [2.6.0](/php/docs/reference/cloud-dlp/2.6.0/V2.HybridFindingDetails)\n- [2.4.1](/php/docs/reference/cloud-dlp/2.4.1/V2.HybridFindingDetails)\n- [2.3.0](/php/docs/reference/cloud-dlp/2.3.0/V2.HybridFindingDetails)\n- [2.2.3](/php/docs/reference/cloud-dlp/2.2.3/V2.HybridFindingDetails)\n- [2.1.0](/php/docs/reference/cloud-dlp/2.1.0/V2.HybridFindingDetails)\n- [2.0.0](/php/docs/reference/cloud-dlp/2.0.0/V2.HybridFindingDetails)\n- [1.19.0](/php/docs/reference/cloud-dlp/1.19.0/V2.HybridFindingDetails)\n- [1.18.0](/php/docs/reference/cloud-dlp/1.18.0/V2.HybridFindingDetails)\n- [1.17.0](/php/docs/reference/cloud-dlp/1.17.0/V2.HybridFindingDetails)\n- [1.16.0](/php/docs/reference/cloud-dlp/1.16.0/V2.HybridFindingDetails)\n- [1.15.1](/php/docs/reference/cloud-dlp/1.15.1/V2.HybridFindingDetails)\n- [1.14.0](/php/docs/reference/cloud-dlp/1.14.0/V2.HybridFindingDetails)\n- [1.13.2](/php/docs/reference/cloud-dlp/1.13.2/V2.HybridFindingDetails)\n- [1.12.0](/php/docs/reference/cloud-dlp/1.12.0/V2.HybridFindingDetails)\n- [1.11.0](/php/docs/reference/cloud-dlp/1.11.0/V2.HybridFindingDetails)\n- [1.10.2](/php/docs/reference/cloud-dlp/1.10.2/V2.HybridFindingDetails)\n- [1.9.0](/php/docs/reference/cloud-dlp/1.9.0/V2.HybridFindingDetails)\n- [1.8.6](/php/docs/reference/cloud-dlp/1.8.6/V2.HybridFindingDetails) \nReference documentation and code samples for the Data Loss Prevention V2 Client class HybridFindingDetails.\n\nPopulate to associate additional data with each finding.\n\nGenerated from protobuf message `google.privacy.dlp.v2.HybridFindingDetails`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Dlp \\\\ V2\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getContainerDetails\n\nDetails about the container where the content being inspected is from.\n\n### hasContainerDetails\n\n### clearContainerDetails\n\n### setContainerDetails\n\nDetails about the container where the content being inspected is from.\n\n### getFileOffset\n\nOffset in bytes of the line, from the beginning of the file, where the\nfinding is located. Populate if the item being scanned is only part of a\nbigger item, such as a shard of a file and you want to track the absolute\nposition of the finding.\n\n### setFileOffset\n\nOffset in bytes of the line, from the beginning of the file, where the\nfinding is located. Populate if the item being scanned is only part of a\nbigger item, such as a shard of a file and you want to track the absolute\nposition of the finding.\n\n### getRowOffset\n\nOffset of the row for tables. Populate if the row(s) being scanned are\npart of a bigger dataset and you want to keep track of their absolute\nposition.\n\n### setRowOffset\n\nOffset of the row for tables. Populate if the row(s) being scanned are\npart of a bigger dataset and you want to keep track of their absolute\nposition.\n\n### getTableOptions\n\nIf the container is a table, additional information to make findings\nmeaningful such as the columns that are primary keys. If not known ahead\nof time, can also be set within each inspect hybrid call and the two\nwill be merged. Note that identifying_fields will only be stored to\nBigQuery, and only if the BigQuery action has been included.\n\n### hasTableOptions\n\n### clearTableOptions\n\n### setTableOptions\n\nIf the container is a table, additional information to make findings\nmeaningful such as the columns that are primary keys. If not known ahead\nof time, can also be set within each inspect hybrid call and the two\nwill be merged. Note that identifying_fields will only be stored to\nBigQuery, and only if the BigQuery action has been included.\n\n### getLabels\n\nLabels to represent user provided metadata about the data being inspected.\n\nIf configured by the job, some key values may be required.\nThe labels associated with `Finding`'s produced by hybrid\ninspection.\nLabel keys must be between 1 and 63 characters long and must conform\nto the following regular expression: `[a-z]([-a-z0-9]*[a-z0-9])?`.\nLabel values must be between 0 and 63 characters long and must conform\nto the regular expression `([a-z]([-a-z0-9]*[a-z0-9])?)?`.\nNo more than 10 labels can be associated with a given finding.\nExamples:\n\n- `\"environment\" : \"production\"`\n- `\"pipeline\" : \"etl\"`\n\n### setLabels\n\nLabels to represent user provided metadata about the data being inspected.\n\nIf configured by the job, some key values may be required.\nThe labels associated with `Finding`'s produced by hybrid\ninspection.\nLabel keys must be between 1 and 63 characters long and must conform\nto the following regular expression: `[a-z]([-a-z0-9]*[a-z0-9])?`.\nLabel values must be between 0 and 63 characters long and must conform\nto the regular expression `([a-z]([-a-z0-9]*[a-z0-9])?)?`.\nNo more than 10 labels can be associated with a given finding.\nExamples:\n\n- `\"environment\" : \"production\"`\n- `\"pipeline\" : \"etl\"`"]]
