Sergey, It is possible, but maybe in your case it's not feasible. Thanks, James
On Friday, June 26, 2015, Sergey Malov <[email protected]> wrote: > Hi James, > From you reply I understand that it is NOT possible to create such a view, > because each family can have different number of columns, and it could be > just one column per family for one PK, and hundreds of thousands for > another PK. How can I possibly accommodate it in a view specification, if I > need to explicitly define column by name ? > Or I misunderstand something ? > > Thank you, > Sergey > > From: James Taylor <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> > Reply-To: "[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>" < > [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> > Date: Friday, June 26, 2015 at 12:04 > To: "[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>" < > [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> > Subject: Re: create a view on existing production table ? > > 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] > <javascript:_e(%7B%7D,'cvml','[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 >> >
