You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2021/02/04 18:11:00 UTC
[jira] [Created] (IMPALA-10475) SYNC_DDL docs should clarify that
it only affects DML
Tim Armstrong created IMPALA-10475:
--------------------------------------
Summary: SYNC_DDL docs should clarify that it only affects DML
Key: IMPALA-10475
URL: https://issues.apache.org/jira/browse/IMPALA-10475
Project: IMPALA
Issue Type: Bug
Components: Docs
Reporter: Tim Armstrong
https://impala.apache.org/docs/build/html/topics/impala_sync_ddl.html
{noformat}
Although INSERT is classified as a DML statement, when the SYNC_DDL option is enabled, INSERT statements also delay their completion until all the underlying data and metadata changes are propagated to all Impala nodes. Internally, Impala inserts have similarities with DDL statements in traditional database systems, because they create metadata needed to track HDFS block locations for new files and they potentially add new partitions to partitioned tables.
{noformat}
I saw someone read this as applying to all tables (Kudu, HBase, etc) but it only inherently applies to traditional non-transactional filesystem-based tables. It also applies to transactional tables until IMPALA-8631 is fixed, after which they will be more strongly consistent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)