@Saurabh I verified in my cluster and I am able to see the table structure. Is the issue specific to views created on huge tables? hive> create view pre_load_table_view as select * from pre_load_table; OK Time taken: 0.386 seconds hive> show create table pre_load_table_view; OK CREATE VIEW `pre_load_table_view` AS select `pre_load_table`.`comp_id`, `pre_load_table`.`item`, `pre_load_table`.`local_supp_code`, `pre_load_table`.`forecast_id`, `pre_load_table`.`transaction_date`, `pre_load_table`.`planned_need_date`, `pre_load_table`.`mfg_partno`, `pre_load_table`.`local_mfg_code`,`pre_load_table`.`forecast_qty_inv`, `pre_load_table`.`forecast_qty_pur`, `pre_load_table`.`purchasing_uom`, `pre_load_table`.`forecast_method`, `pre_load_table`.`b2b_communicated`, `pre_load_table`.`file_name` from `default`.`pre_load_table` Time taken: 0.535 seconds, Fetched: 1 row(s) ... View more

@Raj B If you are using HCatalog with Sqoop, then Sqoop Hive options that are not supported with HCatalog jobs includes (link😞 --hive-import --hive-overwrite Approach is to use hive-import instead of -hcatalog. For example, sqoop import --connect jdbc:mysql://localhost/test --username root --password 'hr' --table sample --hive-import --hive-overwrite --hive-table sqoophive -m 1 --fields-terminated-by '\t' --lines-terminated-by '\n' ... View more

@viswanath For a partitioned table, the idea is as follows: A 'S' lock on table and relevant partition is acquired when a read is being performed. For all other operations, an 'X' lock is taken on the partition. However, if the change is only applicable to the newer partitions, a 'S' lock is acquired on the table, whereas if the change is applicable to all partitions, a 'X' lock is acquired on the table. Thus, older partitions can be read and written into, while the newer partitions are being converted to RCFile. Whenever a partition is being locked in any mode, all its parents are locked in 'S' mode. If you are running 'select' query on the whole of table, then it would wait for the exclusive lock. For more details, refer to link. ... View more

@Saravanan Ramaraj Try collecting the statistics for the table both at table level and column level. Then, try running the queries. Use of stats should improve the performance. Also, refer link1 and link2 for Hive performance tuning. ... View more

@vicky singh Can you share the error you are facing? ... View more

@Ashok Rai Can you please mark as answered to close the thread? ... View more

@Aditya Sirna Try listing the installed packages using yum command: yum list installed | grep mpack ... View more

@Riccardo Iacomini Sure, there are several ORC issues addressed in 2.6.2. ... View more