Hi Sergey, Yes, you can create a Phoenix view over this HBase table, but you have to explicitly list columns by name (i.e. column qualifier) either at view creation time or at read time (using dynamic columns). Also, the row key must conform to what Phoenix expects if there are multiple columns in your PK. Thanks, James
On Wednesday, June 24, 2015, Sergey Malov <[email protected]> wrote: > My apologies if this info can be found somewhere, I don’t see it. > I have a production table “profile” with the following schema : > > {NAME => 'edge', BLOOMFILTER => 'ROW', VERSIONS => '2', IN_MEMORY => > 'false', KEEP_DELETED_CELLS => 'false', DATA_BLOCK_ENCODING => 'FAST_DIFF', > COMPRESSION => 'SNAPPY', TTL => ' > > FOREVER', MIN_VERSIONS => '0', BLOCKCACHE => 'true', BLOCKSIZE => '65536', > REPLICATION_SCOPE => '1'} > > > {NAME => 'export', BLOOMFILTER => 'ROW', VERSIONS => '2', IN_MEMORY => > 'false', KEEP_DELETED_CELLS => 'false', DATA_BLOCK_ENCODING => 'FAST_DIFF', > COMPRESSION => 'SNAPPY', TTL => > > 'FOREVER', MIN_VERSIONS => '0', BLOCKCACHE => 'true', BLOCKSIZE => > '65536', REPLICATION_SCOPE => '1'} > > > {NAME => 'visitor', BLOOMFILTER => 'ROW', VERSIONS => '2', IN_MEMORY => > 'false', KEEP_DELETED_CELLS => 'false', DATA_BLOCK_ENCODING => 'FAST_DIFF', > COMPRESSION => 'SNAPPY', TTL = > > > 'FOREVER', MIN_VERSIONS => '0', BLOCKCACHE => 'true', BLOCKSIZE => > '65536', REPLICATION_SCOPE => '1'} > > > Each of these families can have variable number of column for a given > key, with some having hundreds of thousands columns. > Is it possible to create a Phoenix view for such a table ? > > Thank you, > Sergey Malov >
