Creating Models › Target Servers for Physical Models › Database Property Editors › Hive Physical Property Editors › Hive Support Summary

Hive Support Summary

The following list summarizes support for Hive property page editors. Apart from the basic erwin® Data Modeler physical objects, such as tables, indexes, and triggers, the list includes editors that provide additional support and are used to define more specific Hive property values.

• CTAS
• Database Roles
• Databases
• Domains
• Functions
• Macros
• Tables
• User Ids
• Views
• Permissions

Note:

• For more information about specific Hive property values, refer to the Hive database documentation. The erwin® Data Modeler documentation for the physical property editors provides brief descriptions of the controls on each dialog and tab, which you can use as a point of reference while working with database design features.
• As a best practice, use the PostgreSQL or MySQL ANSI ODBC driver for Reverse Engineering from Database (REDB) while using erwin Data Modeler. Also, for a MySQL ANSI ODBC driver, use version 5.2 and above.
• For PostgreSQL Metastore driver version 9.6.x; for example, 9.6.4, after installing the driver ensure that you clear the Text as LongVarchar and Bool as Char check boxes under Data Type Options.

The following list summarizes the limitations in pure Hive (connection to Hive database directly):

• Reverse engineering from database processing is slow due to the absence of system tables. The required information is retrieved by manual parsing methods instead of a query language.
• User-defined functions are not supported.
• Retrieval of version information using the Hive command is not supported.
• A few index properties, such as deferred rebuild option, idxProperties, and Null Defined As are not supported.