What's New in Apache Kudu
Learn about the new features of Apache Kudu in Cloudera Runtime 7.2.11.
Add --newDatabaseName and --removeImpalaPrefix options
to restore job
While Kudu does not have the notion of a database, users typically define full table names as
<database>.<tablename>. Two new options are added to enable you to
change the existing database name of a restored table or add a new database name to a
restored table. The --newDatabaseName option enables you to specify a new
database name for the restored table. The --removeImpalaPrefix option
removes the impala:: prefix if it exists. The
--newDatabaseName option does not affect the impala::
prefix.
Per-table size and row count limits
Kudu now experimentally supports per-table size limits based on leader disk space usage or
number of rows. When generating new authorization tokens, Masters will now consider the size
limits and strip tokens of INSERT and UPDATE privileges if either limit is reached. To
enable this feature, set the --enable_table_write_limit master flag; adjust
the --table_disk_size_limit and --table_row_count_limit
flags as desired or use the kudu table set_limit tool to set limits per
table.
Improvements
- Backup graphs are sorted by table name to ensure the listing order stays consistent.
- KUDU-3267: The error message output by Kudu Java client in an attempt to write into a non-existent table partition now contains the table’s name.
