@SBandaru Per documentation: Alternately, you can use the pre-2.2 method: Link the HBase configuration file with the Phoenix libraries: ln -sf <HBASE_CONFIG_DIR>/hbase-site.xml /usr/hdp/current/phoenix-client/bin/hbase-site.xml Link the Hadoop configuration file with the Phoenix libraries: ln -sf <HADOOP_CONFIG_DIR>/core-site.xml /usr/hdp/current/phoenix-client/bin/core-site.xml ln -sf >HADOOP_CONFIG_DIR>/hdfs-site.xml /usr/hdp/current/phoenix-client/bin/hdfs-site.xml ... View more

If imported to Hive directly, will the table be available to Pig, MR ? Yes since hive and pig are integrated with HS2 If imported to HCatalog, what needs to be done for accessing via Hive ? Nothing. you should see the table in hive Is pre-creation of tables in Hive necessary ? If yes, what is the advantage of the importing in HCatalog, (I can import in Hive directly)/(import in HDFS and then create external table) ? No. you can use --create-hive-table arguments ... View more

@Khera for all intents and purposes stop using hive CLI. It will soon be deprecated in favor of beeline. Jira here. It does not integrate with ranger so it bypass the security policies. I recommend you only use beeline. ... View more

@Johnny Fugers Hive is great for typically BI queries. The scalability is limitless. When you get into the area of updates, I rather do those activities on phoenix and serve the end results back to hive for BI queries. Hive ACID is coming soon. Until that is available I would use the phoenix->Hive route. Use PIG for ETL. Where it gets interested is using a MPP database on Hadoop. that is where HAWQ comes in. It is a good low latency db engine which provided you some benefits from both hive and phoenix. It does not do all hive & phoenix capabilities. I would say it is a good happy medium. I hope that helps. When you go further into your journey you will start to ask question about security and governance. For security you will start with ranger & Knox. and goverance you will start with falcon/atlas/ranger. ... View more

@subacini balakrishnan did you set delete.topic.enable=true for all brokers? some topic may be undeletable in .9. fixed in .9.1. jira here when you made the delete.topic.enable=true, did you restart ZK and Kafka brokers? ... View more

@Eric Brosch Phoenix is a SQL skin on top of hbase. Phoenix allows to create secondary index on hbase which hbase natively does not create. Phoenix on HDP comes out of the box with hbase. ... View more

@Eric Brosch Phoenix and HDB (HAWQ) may be leveraged in a Lambda architecture. Phoenix supports secondary index and HAWQ is a relational MPP db on HDP. Both can serve low latency queries. Choosing between the two? For know query patterns Phoenix will perform well. For unknown query patterns HAWQ may be your way to go ... View more