[ 
https://issues.apache.org/jira/browse/IMPALA-12899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Becker updated IMPALA-12899:
-----------------------------------
        Parent: IMPALA-10947
    Issue Type: Sub-task  (was: Improvement)

> Temporary workaround for BINARY in complex types
> ------------------------------------------------
>
>                 Key: IMPALA-12899
>                 URL: https://issues.apache.org/jira/browse/IMPALA-12899
>             Project: IMPALA
>          Issue Type: Sub-task
>            Reporter: Daniel Becker
>            Assignee: Daniel Becker
>            Priority: Major
>
> The BINARY type is currently not supported inside complex types and a 
> cross-component decision is probably needed to support it (see IMPALA-11491). 
> We would like to enable EXPAND_COMPLEX_TYPES for Iceberg metadata tables 
> (IMPALA-12612), which requires that queries with BINARY inside complex types 
> don't fail. Enabling EXPAND_COMPLEX_TYPES is a more prioritised issue than 
> IMPALA-11491, so we should come up with a temporary solution, e.g. NULLing 
> BINARY values in complex types and logging a warning, or setting these BINARY 
> values to a warning string.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to