I thought you wanted to have a single physical Phoenix table (backed by a single HBase table) be shared for multiple purposes. If so, views are a good way to do that. You create a regular table in Phoenix and then define views on top of that table based on your requirements. Views share the parent table's PK structure but can add their own columns and indexes.
I'm not 100% sure I'm groking your requirements, though. On Mon, Sep 29, 2014 at 1:07 AM, Nicolas Maillard <nmaill...@hortonworks.com > wrote: > Hello Eli > > Views were one way I was thinking about, but actually what mean is creating > and using an Hbase table like > "mydb:mytable" so either creatng it directly through Phoenix or creating a > view on top of the hbase table to access my phoenix semantics. > Hope this makes sense > > On Fri, Sep 26, 2014 at 4:22 PM, Eli Levine <elilev...@gmail.com> wrote: > > > Views are a good way to reuse a single physical table in Phoenix for > > multiple purposes. They can be used to essentially partition a Phoenix > > table. http://phoenix.apache.org/views.html > > > > Is that something like what you have in mind? > > > > Thanks, > > > > Eli > > > > > > > > > On Sep 25, 2014, at 11:44 PM, Nicolas Maillard < > > nmaill...@hortonworks.com> wrote: > > > > > > Hello everyone > > > > > > I was wondering if phoenix had a way of making use of Hbase namespaces, > > > that is creating a phoenix table is a given namespace, maybe even > > creating > > > this namespace. > > > As we move n more heaby usage of phoenix it makes for a nice way to > > > logically split up tables. > > > > > > regards > > > > > > -- > > > CONFIDENTIALITY NOTICE > > > NOTICE: This message is intended for the use of the individual or > entity > > to > > > which it is addressed and may contain information that is confidential, > > > privileged and exempt from disclosure under applicable law. If the > reader > > > of this message is not the intended recipient, you are hereby notified > > that > > > any printing, copying, dissemination, distribution, disclosure or > > > forwarding of this communication is strictly prohibited. If you have > > > received this communication in error, please contact the sender > > immediately > > > and delete it from your system. Thank You. > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
