<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Phoenix security and initial system table creation in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Phoenix-security-and-initial-system-table-creation/m-p/155366#M117805</link>
    <description>&lt;P&gt;Your understanding is correct. Phoenix delegates to HBase permissions. Secondary index tables would require their own grants as well, yes. They are just another HBase table.&lt;/P&gt;&lt;P&gt;Yes, you have the steps correct regarding the superuser creating the tables and performing grants.&lt;/P&gt;&lt;P&gt;The namespace support actually appears to have landed in 4.8, but this was included in HDP-2.5 which was based on Phoenix 4.7 (the feature was backported) &lt;A href="https://phoenix.apache.org/namspace_mapping.html"&gt;https://phoenix.apache.org/namspace_mapping.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 29 Oct 2016 05:13:49 GMT</pubDate>
    <dc:creator>elserj</dc:creator>
    <dc:date>2016-10-29T05:13:49Z</dc:date>
  </channel>
</rss>

