[
https://issues.apache.org/jira/browse/IMPALA-14906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zoltán Borók-Nagy updated IMPALA-14906:
---------------------------------------
Description:
We can specify columns as non-nullable, e.g.:
{noformat}
CREATE TABLE t (i INT NOT NULL)
STORED AS ICEBERG;
{noformat}
Writers should not write NULLs into such tables. But it can still happen by
non-compliant writers, or incompatible schema changes. In this case Impala
could detect forbidden NULLs during read and raise an error.
was:
We can specify columns as non-nullable, e.g.:
{noformat}
CREATE TABLE t (i INT NOT NULL)
STORED AS ICEBERG;
{noformat}
Writers should not write NULLs into such tables. But it can still happen by
non-compliant writers. In this case Impala could detect forbidden NULLs during
read and raise an error.
> Throw errors on NULL for non-nullable columns
> ---------------------------------------------
>
> Key: IMPALA-14906
> URL: https://issues.apache.org/jira/browse/IMPALA-14906
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Zoltán Borók-Nagy
> Priority: Major
>
> We can specify columns as non-nullable, e.g.:
> {noformat}
> CREATE TABLE t (i INT NOT NULL)
> STORED AS ICEBERG;
> {noformat}
> Writers should not write NULLs into such tables. But it can still happen by
> non-compliant writers, or incompatible schema changes. In this case Impala
> could detect forbidden NULLs during read and raise an error.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
