[yaml] Add use cases for Enrichment transform in YAML

[reeba212]

1. Added a simple bigtable enrichment example
2. Added an end to end use case that demonstrates how spanner IO and enrichment transform coupled with other YAML transforms can be used in a real world setting

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[github-actions]

Assigning reviewers. If you would like to opt out of this review, comment assign to next reviewer:

R: @damccorm for label python.
R: @ahmedabu98 for label io.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

[Polber]

Thanks! Added a few comments

[Polber]

Is this necessary? It is defined in all the transforms, so not sure why it would be required

[Polber]

Just a couple small changes, thanks!

[github-actions]

Reminder, please take a look at this pr: @damccorm @ahmedabu98

[github-actions]

Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment assign to next reviewer:

R: @liferoad for label python.
R: @johnjcasey for label io.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

[github-actions]

Reminder, please take a look at this pr: @liferoad @johnjcasey

[github-actions]

Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment assign to next reviewer:

R: @tvalentyn for label python.
R: @Abacn for label io.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

[damccorm]

@Polber what are next steps on this PR?

@reeba212 it looks like some precommit checks are failing - would you mind taking a look? At a glance, I see:

1. the RAT license check is missing - this is because some files are missing the Apache license
2. Lint/format checks are failing - could you try https://cwiki.apache.org/confluence/display/BEAM/Python+Tips#PythonTips-LintandFormattingChecks
3. test_bigtable_enrichment_yaml seems to be failing

[damccorm]

@Polber @reeba212 friendly reminder to please take a look at this one when you have a chance

[Polber]

You should be able to rebase on master now and pull in the EnrichmentTransform changes

[github-actions]

Reminder, please take a look at this pr: @tvalentyn @Abacn

[github-actions]

Assigning new set of reviewers because Pr has gone too long without review. If you would like to opt out of this review, comment assign to next reviewer:

R: @damccorm for label python.
R: @chamikaramj for label io.

Available commands:

• stop reviewer notifications - opt out of the automated review tooling
• remind me after tests pass - tag the comment author after tests pass
• waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

[damccorm]

R: @Polber

@Polber @reeba212 what are next steps here?

[github-actions]

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

[Polber]

I left a couple comments that should help turn tests green.

This will require rebasing on #33027 once it is merged

[Polber]

1. Add options block with experimental feature
2. Unindent the Expected block
3. Fix the formatting of the expected element (copy the below exactly)

Suggested change

	# Expected:
	# Row(sale_id = 1, customer_id = 1, product_id = 1, quantity = 1, product = Row(product_id: "1", product_name = "pixel 5", product_stock = "2"))
	options:
	yaml_experimental_features: Enrichment
	# Expected:
	# Row(sale_id=1, customer_id=1, product_id=1, quantity=1, product={'product_id': '1', 'product_name': 'pixel 5', 'product_stock': '2'})

[Polber]

1. There is a similar method above this one called _file_io_write_test_preprocessor. You need to add the following to the list in the @YamlExamplesTestSuite.register_test_preprocessor annotation
   • test_bigtable_enrichment_yaml
   • test_enrich_spanner_with_bigquery_yaml

Should look very similar to the change on line 159 above

[Polber]

Add Expected block:

Suggested change

	# Expected:
	# Row(customer_id=1001, customer_name='Alice', customer_email='[email protected]', product_id=2001, order_date='24-03-24', order_amount=150)
	# Row(customer_id=1003, customer_name='Claire', customer_email='[email protected]', product_id=2003, order_date='7-05-24', order_amount=110)