kudu注意事项

1、Kudu细节摘要
1.1、注意细节（kudu官网链接）
    1. Columns withDOUBLE,FLOAT, orBOOLtypes are not allowed as part of a primary key definition. Additionally, all columns that are part of a primary key definition must beNOT NULL.（DOUBLE, FLOAT, or BOOL types 不允许作为主键）
    2. CHARand complex types likeARRAY,MAP, andSTRUCTare not yet supported.（kudu不支持复杂类型）
    3. Type, nullability and type attributes (i.e. precision and scale ofDECIMAL, length ofVARCHAR) of existing columns cannot be changed by altering the table.（类型不能改变）
    4. Tables can have a maximum of 300 columns by default.（默认情况下，每个表最大列 300列）
    5. Tables must have an odd number of replicas, with a maximum of 7.（副本数必须为奇数，最大值为7个副本）
    6. By default, cells cannot be larger than 64KiB before encoding or compression.（默认情况下，未编码和压缩情况下，单元格的值不能大于64KB）
    7. Dropping a column does not immediately reclaim space. Compaction must run first.（删除表的一列，不能立即释放空间）
    8. There is no way to run compaction manually, but dropping the table will reclaim the space immediately.（删除表能立即释放空间）
    9. Kudu has a requirement on having the server-side clock synchronized with NTP. Kudu masters and tablet servers crash if detecting that the clock is out of sync. For the clock synchronization, either synchronize the local clock using an NTP server such asntpdorchronyd, or use the built-in NTP client for Kudu masters and tablet servers.（Kudu masters and tablet servers 严格依赖 NTP时钟同步）
    10. If a tablet server has a very large number of tablets, it may take several minutes to start up. It is recommended to limit the number of tablets per server to 1000 or fewer. Consider this limitation when pre-splitting your tables. If you notice slow start-up times, you can monitor the number of tablets per server in the web UI.（启动太慢，推荐限制每个机器上tablet 1000或者更少）
    11. If the WHERE clause of your query includes comparisons with the operators =, <=, '\<', '\>', >=, BETWEEN, or IN, Kudu evaluates the condition directly and only returns the relevant results. This provides optimum performance, because Kudu only returns the relevant results to Impala. For predicates !=, LIKE, or any other predicate type supported by Impala, Kudu does not evaluate the predicates directly, but returns all results to Impala and relies on Impala to evaluate the remaining predicates and filter the results accordingly. This may cause differences in performance, depending on the delta of the result set before and after evaluating the WHERE clause.（如果查询的WHERE子句中包含使用=、<=、<、>、>=、BETWEEN或IN运算符的比较，Kudu会直接评估条件并仅返回相关结果。这提供了最佳的性能，因为Kudu只将相关结果返回给Impala。对于!=、LIKE或Impala支持的任何其他谓词类型，Kudu不直接评估谓词，而是将所有结果返回给Impala，并依赖Impala来评估剩余的谓词并相应地过滤结果。这可能会导致性能差异，具体取决于在评估WHERE子句之前和之后结果集的增量。）
    12. partitioning_rules_of_thumb：
    13. Updates, inserts, and deletes via Impala are non-transactional. If a query fails part of the way through, its partial effects will not be rolled back.（非事务）
    14. The maximum parallelism of a single query is limited to the number of tablets in a table. For good analytic performance, aim for 10 or more tablets per host for large tables.（性能优化方面）
    15. decimal(18,2)：Precision This value must be between 1 and 38 and has no default;Scale :This value must be between 0 and the precision，The precision and scale of decimal columns cannot be changed by altering the table.（ decimal(18,20) 类型中，后面的值必须小于等于 前面的值）