H, My approach to have a SQL engine on top of Hbase has been (excluding Spark & Phoenix for now) is to create Hbase table as is, then create an EXTERNAL Hive table on Hbase using Hadoop.hive.HbaseStorageHandler to interface with Hbase table.
My reasoning with creating Hive external table is to avoid accidentally dropping Hbase table etc. Is this a reasonable approach? Then that Hive table can be used by a variety of tools like Spark, Tableau, Zeppelin. Is this a viable solution as Hive seems to be preferred on top of Hbase compared to Phoenix etc. Thaks Dr Mich Talebzadeh LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>* http://talebzadehmich.wordpress.com *Disclaimer:* Use it at your own risk. Any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on this email's technical content is explicitly disclaimed. The author will in no case be liable for any monetary damages arising from such loss, damage or destruction.
