AWS redshift documentation change
Summary
Removed references to 'enable_case_sensitive_identifier' configuration option and updated examples to only use 'enable_case_sensitive_super_attribute' for case-sensitive SUPER data queries.
Security assessment
Changes involve configuration simplification and query syntax updates without any security vulnerability fixes or security feature additions. Modifications focus on documentation clarity for case-sensitive attribute handling.
Diff
diff --git a/redshift/latest/dg/super-examples.md b/redshift/latest/dg/super-examples.md index 5949ca9fc..ff0845f94 100644 --- a//redshift/latest/dg/super-examples.md +++ b//redshift/latest/dg/super-examples.md @@ -7 +7 @@ -Loading semi-structured dataQuerying nested semi-structured dataUsing enable_case_sensitive_identifier and enable_case_sensitive_super_attribute with semi-structured dataFiltering semi-structured dataUnnesting semi-structured dataUnnesting nested arraysUsing semi-structured data in subqueriesAggregating queries using semi-structured dataUsing semi-structured data in materialized viewsUsing PIVOT and UNPIVOT with semi-structured data +Loading semi-structured dataQuerying nested semi-structured dataUsing enable_case_sensitive_super_attribute with semi-structured dataFiltering semi-structured dataUnnesting semi-structured dataUnnesting nested arraysUsing semi-structured data in subqueriesAggregating queries using semi-structured dataUsing semi-structured data in materialized viewsUsing PIVOT and UNPIVOT with semi-structured data @@ -17 +17 @@ The following examples demonstrate how to work with semi-structured data in Amaz -We recommend that you set the `enable_case_sensitive_identifier` and `enable_case_sensitive_super_attribute` configuration options before working with the SUPER data type. For more information, see [enable_case_sensitive_identifier](./r_enable_case_sensitive_identifier.html) and [enable_case_sensitive_super_attribute](./r_enable_case_sensitive_super_attribute.html). +We recommend that you set the `enable_case_sensitive_super_attribute` configuration option to true before working with the SUPER data type. For more information, see [enable_case_sensitive_super_attribute](./r_enable_case_sensitive_super_attribute.html). @@ -27 +26,0 @@ The following statements create a sample table and load a sample JSON object int - SET enable_case_sensitive_identifier TO true; @@ -350 +349 @@ The following statements -## Using `enable_case_sensitive_identifier` and `enable_case_sensitive_super_attribute` with semi-structured data +## Using `enable_case_sensitive_super_attribute` with semi-structured data @@ -352 +351 @@ The following statements -The following examples show how the configuration options [enable_case_sensitive_identifier](./r_enable_case_sensitive_identifier.html) and [enable_case_sensitive_super_attribute](./r_enable_case_sensitive_super_attribute.html) differ when used for querying semi-structured data. For more information on these configuration options, see [Accessing JSON fields with uppercase and mixed-case field names or attributes](./super-configurations.html#upper-mixed-case). +The following examples show how the [enable_case_sensitive_super_attribute](./r_enable_case_sensitive_super_attribute.html) configuration option affects querying semi-structured data. For more information, see [Accessing JSON fields with uppercase and mixed-case field names or attributes](./super-configurations.html#upper-mixed-case). @@ -354 +353 @@ The following examples show how the configuration options [enable_case_sensitive -In the following statement, resetting both configuration options to their default of false makes the query return NULL. +In the following statement, resetting the configuration option to its default of false makes the query return NULL for mixed-case attribute names. @@ -357 +355,0 @@ In the following statement, resetting both configuration options to their defaul - RESET enable_case_sensitive_identifier; @@ -368 +366 @@ In the following statement, resetting both configuration options to their defaul -In following example, the sample query returns the desired result after you wrap the case sensitive attributes in double quotation marks and set `enable_case_sensitive_identifier` to true. +In the following example, the sample query returns the desired result after you set `enable_case_sensitive_super_attribute` to true. No double quotation marks around attribute names are needed. @@ -371,35 +368,0 @@ In following example, the sample query returns the desired result after you wrap - RESET enable_case_sensitive_identifier; - RESET enable_case_sensitive_super_attribute; - - SELECT - all_data.data.pnr.events[0]."eventType" - FROM test_json; - - eventtype - ----------- - NULL - - SET enable_case_sensitive_identifier TO true; - - SELECT - all_data.data.pnr.events[0]."eventType" - FROM test_json; - - eventtype - ----------- - "UPDATED" - -In the following example, the sample query returns the desired result after you set `enable_case_sensitive_super_attribute` to true without wrapping the case sensitive attributes in double quotation marks. - - - RESET enable_case_sensitive_identifier; - RESET enable_case_sensitive_super_attribute; - - SELECT - all_data.data.pnr.events[0].eventType - FROM test_json; - - eventtype - ----------- - NULL - @@ -483 +446 @@ For examples of unnesting semi-structured data using UNNEST in the FROM clause, - c."emailContacts" d, + c.emailContacts d, @@ -506 +469 @@ The following statement uses a subquery in the WHERE clause to return only a sub - c."emailContacts" d + c.emailContacts d