You still have to register the view to phoenix and define which CF's and
columns you are accessing, so this isn't entirely free form...
"myTable" ("cf" VARCHAR primary key,
"cf"."attr1" VARCHAR, "cf"."attr2"
… however, "myTable" in the above example is the HBase table you created
outside Phoenix, so Phoenix doesn't need to copy any data, etc..
On 7/10/13 10:13 PM, "Bing Jiang" <[EMAIL PROTECTED]> wrote:
>If build view upon Phoenix uncontrolled tables, whether it can be used to
>column family or qualifier?
>I want to know your design details.
>2013/7/11 Doug Meil <[EMAIL PROTECTED]>
>> Hi folks,
>> I just wanted to give a shout out to the Phoenix framework, and
>> specifically for the ability to create "view" against an HBase table
>> schema was not being managed by Phoenix. That's a really nice feature
>> I'm not sure how many folks realize this. I was initially nervous that
>> this was only for data created with Phoenix, but that's not the case,
>> you're looking for a lightweight framework for SQL-on-HBase I'd check it
>> out. For this particular scenario it's probably better for ad-hoc data
>> exploration, but often that's what people are looking to do.
>> Doug Meil
>> Chief Software Architect, Explorys
>> [EMAIL PROTECTED]
>National Research Center for Intelligent Computing Systems
>Institute of Computing technology
>Graduate University of Chinese Academy of Science