Specify insert fields and unique indices for Rekognition tags insert

[AetherUnbound]

Fixes

Fixes #4947 by @AetherUnbound

Description

This PR specifies both the target_fields and replace_index directives for the PostgresHook's insert_rows function. Both fields are required when using replace=True to upsert the rows.

I've replaced one of the records in our test set to include a duplicate match on identifier in order to test this behavior.

Testing Instructions

If you remove the change to the add_rekognition_labels.py file, you can use the following to cause the error in the linked issue locally:

1. Run ov just down -v to clear everything
2. Add the following values to your catalog/.env file:

# S3 prefix location for the Rekognition dataset
AIRFLOW_VAR_REKOGNITION_DATASET_PREFIX=image_analysis_labels.jsonl
# In-memory buffer size for processing Rekognition data
AIRFLOW_VAR_REKOGNITION_MEMORY_BUFFER_SIZE=25
# File buffer size for reading Rekognition data from S3
AIRFLOW_VAR_REKOGNITION_FILE_BUFFER_SIZE=16384

3. Run ov just api/init to initialize the catalog database with data
4. Run ov just c to start the catalog services
5. Enable the batched_update DAG
6. Trigger a run of add_rekognition_labels and wait for it to fail

Reapplying the change and rerunning the above steps should then allow the add_rekognition_labels DAG to succeed.

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (ov just catalog/generate-docs for catalog
  PRs) or the media properties generator (ov just catalog/generate-docs media-props
  for the catalog or ov just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[stacimc]

Verified that I could see the error, and that it works when the changes are back in. 🚀

[krysal]

Everything worked as expected with the test steps. Nice catch!