[ https://issues.apache.org/jira/browse/IMPALA-10475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17279081#comment-17279081 ]
shajini thayasingh commented on IMPALA-10475: --------------------------------------------- [~tarmstrong] so can I just add this statement "{color:#de350b}_SYNC_DDL only applies to traditional non-transactional filesystem-based tables and does not apply to tables such as Kudu, HBase, etc_{color}"? I will add this statement following the para you have called out in the description " Although {{INSERT}} is classified as a DML statement, when the {{SYNC_DDL}} option is ----------" In the long run SYNC_DDL will not apply to "Transactional tables" so I am considering NOT to mention "transactional tables". Please share your opinion here. > 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: Task > Components: Docs > Reporter: Tim Armstrong > Assignee: shajini thayasingh > Priority: Major > > 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) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org