Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Can Phoenix v4.4 utilize HBase namespaces?

Solved Go to solution
Highlighted

Can Phoenix v4.4 utilize HBase namespaces?

Contributor

As we've been evaluating the use of Phoenix + HBase in HW 2.3, we came upon the conclusion that in the current bundled version of Phoenix, 4.4, that namespaces are not supported. The upstream JIRAs are confusing but it looks like Phoenix will not support namespaces + permissions until 4.7-4.8.

Does this sound like a correct conclusion? If so what are my options in terms of Phoenix?

  • upgrade it within HW 2.3 (assuming this is not an option)?
  • work around it somehow?
  • Move Phoenix tables manually out of default NS into our applications? How?

This is what we seen when enabling Phoenix on our system. The SYSTEM.* tables are Phoenix's. Ours are in the ns: namespace.

Version 1.1.2.2.3.6.0-3796, r2873b074585fce900c3f9592ae16fdd2d4d3a446, Thu Jun 23 16:29:31 UTC 2016

hbase(main):001:0> list
TABLE
SYSTEM.CATALOG
SYSTEM.FUNCTION
SYSTEM.SEQUENCE
SYSTEM.STATS
ambarismoketest

ns:contact
ns:counters
ns:counters-backup
ns:lists
ns:logins
ns:modelLogs
ns:models
ns:reportLogs
ns:users
References
1 ACCEPTED SOLUTION

Accepted Solutions

Re: Can Phoenix v4.4 utilize HBase namespaces?

Mentor

Phonenix 4.7 is going to be part of HDP 2.5. namespaces will be one of the features.

3 REPLIES 3

Re: Can Phoenix v4.4 utilize HBase namespaces?

Mentor

Phonenix 4.7 is going to be part of HDP 2.5. namespaces will be one of the features.

Re: Can Phoenix v4.4 utilize HBase namespaces?

Contributor

http://hortonworks.com/blog/odpi-core-hdp-hadoop-core/. Looks with the above that Phoenix would be part of the extended HDP services.

> Extended HDP services: Extended HDP services relates to the services that access the data stored in HDP including Hive, HBase, Storm, Spark and more. Extended services provide customers with the flexibility to uptake the innovation that is delivered on top of the common core, based on their own requirements and schedule. With Extended services, customers would be able to easily uptake the new functionality without causing any disruption to their core platform.

Re: Can Phoenix v4.4 utilize HBase namespaces?

Mentor

That's correct, idea is that you won't need to wait for major releases when innovative features like namespaces trickle down from community. We will ship non-core features more often than HDFS and YARN.