You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Randy Gelhausen (JIRA)" <ji...@apache.org> on 2016/01/27 05:58:39 UTC
[jira] [Created] (PHOENIX-2632) Easier Hive->Phoenix data movement
Randy Gelhausen created PHOENIX-2632:
----------------------------------------
Summary: Easier Hive->Phoenix data movement
Key: PHOENIX-2632
URL: https://issues.apache.org/jira/browse/PHOENIX-2632
Project: Phoenix
Issue Type: Improvement
Reporter: Randy Gelhausen
Moving tables or query results from Hive into Phoenix today requires error prone manual schema re-definition inside HBase storage handler properties.
Since Hive and Phoenix support near equivalent types, it should be easier for users to pick a Hive table and load it (or derived query results) from it.
I'm posting this to open design discussion, but also submit my own project https://github.com/randerzander/HiveToPhoenix for consideration as an early solution. It creates a Spark DataFrame from a Hive query, uses Phoenix JDBC to "create if not exists" a Phoenix equivalent table, and uses the phoenix-spark artifact to store the DataFrame into Phoenix.
I'm eager to get feedback if this is interesting/useful to the Phoenix community.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)