Abacn commented on code in PR #40663:
URL: https://github.com/apache/beam/pull/40663#discussion_r4318103738


##########
CHANGES.md:
##########
@@ -80,10 +80,10 @@
 * (Python) Added `AwsOptions` with `--aws_*` pipeline options (e.g. 
`--aws_access_key_id`, `--aws_region_name`, `--aws_endpoint_url`) that set 
defaults for all AWS service clients. The existing `--s3_*` options in 
`S3Options` override these defaults for the S3 client only 
([#40528](https://github.com/apache/beam/issues/40528)).
 * (Python) Added `--aws_credentials_secret_manager` so AWS credentials 
(`--aws_access_key_id`, `--aws_secret_access_key`, `--aws_session_token` and 
their `--s3_*` overrides) can be secret specs resolved through a secret manager 
such as `GoogleCloudSecretManager`, instead of plain-text values 
([#40528](https://github.com/apache/beam/issues/40528)).
 * (Python) Added `AwsSecret` (`AwsSecretsManager` / `type:awssecret`) to 
retrieve secrets from AWS Secrets Manager, configured from `AwsOptions` 
(`--aws_*`) with optional per-secret connection overrides 
([#40528](https://github.com/apache/beam/issues/40528)).
-* (Go) Added `schema.RegisterLogicalTypeConversion` and 
`schema.RegisterLogicalTypeCoder` to register portable logical types in one 
call, and Go types for the standard `beam:logical_type:date:v1` and 
`beam:logical_type:micros_instant:v1` logical types, so schemas from other SDKs 
with these types can be used in cross-language pipelines 
([#39684](https://github.com/apache/beam/issues/39684)).
 
 ## Breaking Changes
 
+* (Java) Removed Beam SQL Google Cloud Data Catalog table provider 
(`beam-sdks-java-extensions-sql-datacatalog`) because GCP Data Catalog has been 
decommissioned ([#35514](https://github.com/apache/beam/issues/35514)).

Review Comment:
   Let's just use this PR number as the reference change number. Current linked 
to a generic test failure issue isn't a good reference



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to