1

I have scanned a Bigquery table from Google DLP Console. The scan results are saved back into a big query table. DLP has identified sensitive information, but the row_index is shown as null "location.content_locations.record_location.table_location.row_index", can anyone help me understand why?

Manish Kumar Mishra
  • 23
  • 2
  • Can you add a little more detail to your question ? Like table structure, what were you looking for etc. – Wojtek_B Apr 20 '21 at 14:40

1 Answers1

1

We no longer populate row_index for bigquery as it's not meaningful since BQ is unordered. If you want to identify the row where the finding came from, I suggest using identifyingFields which lives in BigQueryOptions when you create your job.

https://cloud.google.com/dlp/docs/creating-job-triggers#job-identifying-fields

Jordanna Chord
  • 950
  • 5
  • 12