John Russell has posted comments on this change. Change subject: IMPALA-1654: DDL for multiple partitions ......................................................................
Patch Set 3: (2 comments) http://gerrit.cloudera.org:8080/#/c/5726/3/docs/topics/impala_alter_table.xml File docs/topics/impala_alter_table.xml: Line 144: For example, you might drop a group of partitions corresponding to a particular date > should we warn user about the scalability limit (multiple hms RPCs) of curr Does the scalability bottleneck apply when the number of matching partitions is high, or just generally when the table has a lot of partitions regardless of how many match? Do we have any guidance to offer (e.g. "don't use this idiom on tables with tens of thousands of partitions", or "under circumstances XYZ, issue multiple ALTER TABLE statements, each for one partition")? Does any issue manifest itself just as a single slow DDL statement, or does the hms traffic potentially cause other statements to wait, or other symptoms? http://gerrit.cloudera.org:8080/#/c/5726/3/docs/topics/impala_compute_stats.xml File docs/topics/impala_compute_stats.xml: Line 130: The following <codeph>COMPUTE INCREMENTAL STATS</codeph> statements affect some but not all > trailing space. Done -- To view, visit http://gerrit.cloudera.org:8080/5726 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-MessageType: comment Gerrit-Change-Id: I2060552d5081e5f93b1b1f398414c52fa03f215b Gerrit-PatchSet: 3 Gerrit-Project: Impala-ASF Gerrit-Branch: master Gerrit-Owner: John Russell <jruss...@cloudera.com> Gerrit-Reviewer: Alex Behm <alex.b...@cloudera.com> Gerrit-Reviewer: Amos Bird <amosb...@gmail.com> Gerrit-Reviewer: John Russell <jruss...@cloudera.com> Gerrit-HasComments: Yes