Cloudera Community

Support Questions

Find answers, ask questions, and share your expertise
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search

Who agreed with this topic

How to disable hive managed tables from becoming transactional/insert-only tables in HDP 3.x. Blocking migration to HDP 3.x

Labels:
avatar
author-rank anirban_chatter
New Contributor

Created ‎04-05-2019 05:13 AM

a 'create table ..' command in HDP 3.x results in the table becoming transactional/insert-only table.

+----------------------------------------------------+

| createtab_stmt |

+----------------------------------------------------+

| CREATE TABLE `ytemp.emps`( |

| `empid` int, |


| ROW FORMAT SERDE |

| 'org.apache.hadoop.hive.ql.io.orc.OrcSerde' |

| STORED AS INPUTFORMAT |

| 'org.apache.hadoop.hive.ql.io.orc.OrcInputFormat' |

| OUTPUTFORMAT |

| 'org.apache.hadoop.hive.ql.io.orc.OrcOutputFormat' |

| LOCATION |

| 'hdfs://xxxx/ytemp.db/emps' |

| TBLPROPERTIES ( |

| 'bucketing_version'='2', |

| 'transactional'='true', |

| 'transactional_properties'='insert-only', |

| 'transient_lastDdlTime'='1554244939') |

+----------------------------------------------------+

tables created by 'create table .' command did not have the 'transactional'='true', 'transactional_properties'='insert-only', in HDP 2.x.

These types of tables (transactional) are not readable by Spark or Presto.

I understand, that this is the default behavior in HDP 3.x. But this breaks backward compatibility with HDP 2.x (where Hive managed tables were not transactional tables by default).

Can someone please recommend a way to disable hive managed tables becoming transactional?, as this is a big impediment for migrating to HDP 3.x from HDP 2.x

Note: I don't want to create 'external tables'

3,337
1
Who agreed with this topic