pitrou commented on PR #45462: URL: https://github.com/apache/arrow/pull/45462#issuecomment-2757322484
> This adds a user-friendly notation for nested fields: > * Columns `col.key` and `col.value` can be used to reference they key and value nested field of a `MapType` column. Currently, `col.key_value.key` and `col.key_value.value` are required, respectively. Is this useful? Is there a reasonable use case for using different encryption settings for the map key and value columns, respectively? Otherwise I think we can only keep the following items, which will also simplify the semantics and the implementation: > * Columns `col.element` can be used to reference they individual list elements of a `ListType` column. Currently, `col.list.element` is required. > * The actual column name can be used to encrypt all nested fields with the same encryption key. > * The current column naming scheme can still be used for backward compatibility. -- 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]
