You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by Nicolas Maillard <nm...@hortonworks.com> on 2014/10/01 21:28:47 UTC
Re: Hbase namespaces
Hello eli
Thank yo for the insight. My requirement is actually to have a database
like system in phoenix. essentialy leveraging Hbase namespaces. This is in
the whole bringing up in phoenix Hbase new features.
I was thinking adding to the antr schema something like create myDb.myTable
construct to be able to create phoenix/Hbase tables that are not in the
default namespace or in the view part creating a view on an Hbase table
that is not in the default hbase namespace.
Does this make more sense ?
If nothing has been done and it is a valid feature maybe I could take a
strike if there are other ways I would love to know.
Hope this is clearer
On Mon, Sep 29, 2014 at 5:22 PM, Eli Levine <el...@gmail.com> wrote:
> 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 <
> nmaillard@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 <el...@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 <
> > > nmaillard@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.
> >
>
--
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.
Re: Hbase namespaces
Posted by Nicolas Maillard <nm...@hortonworks.com>.
Hello Eli
Great I will file a Jira and take a stab at it.
I will first finally push my first version of hive to phoenix connector,
probably this weekend and will take the namespace right after.
thanks
On Wed, Oct 1, 2014 at 9:44 PM, Eli Levine <el...@gmail.com> wrote:
> Ah I see what you mean. Currently HBase namespaces (HBASE-8015) are not
> surfaced/used by Phoenix. It think it would be an interesting feature
> request. Phoenix has the concept of table schemas and they are currently
> used to construct the underlying HBase tables' names. One possibility is to
> map Phoenix schemas to HBase namespaces.
>
> Want to file a Jira? If you want to take a stab at implementation that
> would be great, too. Would require a bit of thought with respect to design
> and how HBase namespaces are surfaced to Phoenix users.
>
> Thanks,
>
> Eli
>
>
>
>
> On Wed, Oct 1, 2014 at 12:28 PM, Nicolas Maillard <
> nmaillard@hortonworks.com
> > wrote:
>
> > Hello eli
> >
> > Thank yo for the insight. My requirement is actually to have a database
> > like system in phoenix. essentialy leveraging Hbase namespaces. This is
> in
> > the whole bringing up in phoenix Hbase new features.
> > I was thinking adding to the antr schema something like create
> myDb.myTable
> > construct to be able to create phoenix/Hbase tables that are not in the
> > default namespace or in the view part creating a view on an Hbase table
> > that is not in the default hbase namespace.
> > Does this make more sense ?
> > If nothing has been done and it is a valid feature maybe I could take a
> > strike if there are other ways I would love to know.
> >
> > Hope this is clearer
> >
> > On Mon, Sep 29, 2014 at 5:22 PM, Eli Levine <el...@gmail.com> wrote:
> >
> > > 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 <
> > > nmaillard@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 <el...@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 <
> > > > > nmaillard@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.
> > > >
> > >
> >
> > --
> > 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.
Re: Hbase namespaces
Posted by Eli Levine <el...@gmail.com>.
Ah I see what you mean. Currently HBase namespaces (HBASE-8015) are not
surfaced/used by Phoenix. It think it would be an interesting feature
request. Phoenix has the concept of table schemas and they are currently
used to construct the underlying HBase tables' names. One possibility is to
map Phoenix schemas to HBase namespaces.
Want to file a Jira? If you want to take a stab at implementation that
would be great, too. Would require a bit of thought with respect to design
and how HBase namespaces are surfaced to Phoenix users.
Thanks,
Eli
On Wed, Oct 1, 2014 at 12:28 PM, Nicolas Maillard <nmaillard@hortonworks.com
> wrote:
> Hello eli
>
> Thank yo for the insight. My requirement is actually to have a database
> like system in phoenix. essentialy leveraging Hbase namespaces. This is in
> the whole bringing up in phoenix Hbase new features.
> I was thinking adding to the antr schema something like create myDb.myTable
> construct to be able to create phoenix/Hbase tables that are not in the
> default namespace or in the view part creating a view on an Hbase table
> that is not in the default hbase namespace.
> Does this make more sense ?
> If nothing has been done and it is a valid feature maybe I could take a
> strike if there are other ways I would love to know.
>
> Hope this is clearer
>
> On Mon, Sep 29, 2014 at 5:22 PM, Eli Levine <el...@gmail.com> wrote:
>
> > 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 <
> > nmaillard@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 <el...@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 <
> > > > nmaillard@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.
> > >
> >
>
> --
> 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.
>