AWS redshift documentation change
Summary
Added documentation about handling non-lowercase identifiers in streaming materialized views and workarounds for automatic/manual refreshes
Security assessment
The change addresses a functional limitation with case sensitivity in identifiers and provides configuration guidance. There is no evidence of a security vulnerability being addressed or security features being documented.
Diff
diff --git a/redshift/latest/dg/materialized-view-streaming-ingestion.md b/redshift/latest/dg/materialized-view-streaming-ingestion.md index 6c26ec22f..0467c7ab4 100644 --- a//redshift/latest/dg/materialized-view-streaming-ingestion.md +++ b//redshift/latest/dg/materialized-view-streaming-ingestion.md @@ -63,0 +64,10 @@ Feature or behavior | Description +**Non-lowercase identifiers** | When creating streaming materialized views on Amazon Managed Streaming for Apache Kafka topics or Kinesis Data Streams that contain non-lowercase identifiers, automatic refreshes might fail. To resolve this, do one of the following: + + * Use manual refreshes with the `enable_case_sensitive_identifier` parameter set to `true` + * Enable automatic refreshes by setting `enable_case_sensitive_identifier` to `true` at the database or cluster level + + + +###### Note + +Setting `enable_case_sensitive_identifier` at the user level isn't sufficient for automatic refreshes, but will work for manual refreshes. For more information about case-sensitive identifiers, see [enable_case_sensitive_identifier](./r_enable_case_sensitive_identifier.html).