Page History

...

NONE = disable the datanucleus level 2 cache, SOFT = soft reference based cache, WEAK = weak reference based cache.
Warning note: For most Hive installations, enabling the datanucleus cache can lead to correctness issues, and is dangerous. This should be left  as as "none".

datanucleus.identifierFactory

...

Same as hive.metastore.try.direct.sql, for read statements within a transaction that modifies metastore data. Due to non-standard behavior in Postgres, if a direct SQL select query has incorrect syntax or something similar inside a transaction, the entire transaction will fail and fall-back to DataNucleus will not be possible. You should disable the usage of direct SQL inside transactions if transactions if that happens in your case.

This can be configured on a per client basis by using the "set metaconf:hive.metastore.try.direct.sql.ddl=<value>" command, starting with Hive 0.14.0 (HIVE-7532). 

hive.direct.sql.max.query.length 

• Default Value: 100
• Added In: Hive 1.3.0 and 2.1.0 (but not 2.0.x) with HIVE-12349

The maximum size of a query string (in KB) as generated by direct SQL. 

hive.direct.sql.max.elements.in.clause

...

• Default Value: 1000
• Added In: Hive 1.3.0 and 2.1.0 (but not 2.0.x) with HIVE-12349

The maximum number of values in a an IN clause as generated by direct SQL. Once exceeded, it will be broken into multiple OR separated IN clauses. 

hive.direct.sql.max.elements.values.clause

• Default Value: 1000
• Added In: Hive 1.3.0 and 2.1.0 (but not 2.0.x) with HIVE-12349

...

The maximum number of values in a VALUES clause for an INSERT statement as generated by direct SQL.

...