You can map HBase composite row key to Phoenix primary key only if serialization used for HBase matches with Phoenix. Ex: leading 1 byte for bucket, 0-byte char for separating columns, etc.
If you used a different mechanism to serialize rowkey in HBase, you can still map it Phoenix table but declare PK as VARBINARY and see if you can create a UDF to separate columns. On Tuesday, July 21, 2015, Anchal Agrawal <anc...@yahoo-inc.com> wrote: > Hi, > > I'm trying to map an existing HBase table to Phoenix. Can the existing > HBase table's rowkey be imported as the rowkey of the Phoenix table? On > this page ( > https://phoenix.apache.org/faq.html#How_I_map_Phoenix_table_to_an_existing_HBase_table), > there's an example: > > CREATE VIEW t1 ( pk VARCHAR PRIMARY KEY, f1.val VARCHAR ) > > Here, is pk the HBase table's column that's being used as the primary > key, or is it a Phoenix keyword/placeholder to refer to the HBase table's > rowkey? My table's rowkey is made up of several fields that are not stored > as columns in that table. If I could just import the rowkey into Phoenix, > that'd be great. > > Thank you! > > Sincerely, > Anchal >
