You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Arnab Karmakar (Jira)" <ji...@apache.org> on 2026/07/28 09:01:00 UTC
[jira] [Created] (IMPALA-15225) Add DEFAULT keyword for Iceberg V3 default values
Arnab Karmakar created IMPALA-15225:
---------------------------------------
Summary: Add DEFAULT keyword for Iceberg V3 default values
Key: IMPALA-15225
URL: https://issues.apache.org/jira/browse/IMPALA-15225
Project: IMPALA
Issue Type: Improvement
Components: Backend, Frontend
Reporter: Arnab Karmakar
Add DEFAULT keyword support for Iceberg V3 default values for queries like:
{code:java}
INSERT INTO orders VALUES (101, DEFAULT, DEFAULT);
UPDATE … SET status = DEFAULT WHERE …; {code}
This ticket is currently on hold because this requires Calcite support.
`{{{}KW_DEFAULT`{}}} is currently in {{{}`ident_or_unreserved{}}}` and it can appear as a column reference [(link)|https://github.com/apache/impala/blob/05ffd62a742a7bc21990b0777962b29cfce0fdb3/fe/src/main/cup/sql-parser.cup#L4558]. If we also try to use bare {{KW_DEFAULT}} as a value-expression in the same grammar, we get a ** conflict. Its because Impala uses LALR(1) parser that causes ambiguity when adding the new keyword.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)