Thank you James this one works for me too but my case little bit more complex my key is <4byte><4byte><4byte><8byte><array[0..N of 8bytes members]> I manage to project properly <4byte><4byte><4byte><8byte> but <array[0..N of 8bytes members]> part keep figting me :)
Is it possible to have array of \x00\x00\x00\x01\x00\x00\x00\x01 elements and what is proper way to surface it in the view and be able to have WHERE on it with regex on bytes? [?] On Thu, Mar 5, 2015 at 3:44 PM, James Taylor <[email protected]> wrote: > This worked fine for me. > In HBase shell: > create 't1', {NAME => 'f1'} > > In Phoenix sqlline: > create view v1(a VARCHAR PRIMARY KEY, "f1".b INTEGER) as select * from > "t1"; > create view v2(a VARCHAR PRIMARY KEY, "f1".c INTEGER) as select * from > "t1"; > > If your table name and column family name are not upper case, make > sure you surround them by double quotes when referencing in your > statement. You can also declare a default column family like this > instead: > > create view v3(a VARCHAR PRIMARY KEY, d INTEGER) as select * from "t1" > default_column_family='f1'; > > Thanks, > James > > On Thu, Mar 5, 2015 at 8:19 AM, Sergey Belousov > <[email protected]> wrote: > > Hi All > > > > It seems like impossible now to create more than one view (with different > > names and columns of course) on top of existent HBase table. > > > > It also seems impossible to provide view name other than original HBase > > table name you base you view of. > > > > Are thouse statements correct or I just missing something? and if they > are > > is it something that can be implemented in historicity short time to > make it > > possible? Is it even possible or there is some big underlying issues that > > will stop it from happening? > > > > > > Thank you > > >
