<?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: Best practice architecture and naming hdfs path names/hive database for dev and test on 1 cluste in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/Best-practice-architecture-and-naming-hdfs-path-names-hive/m-p/58353#M49793</link>
    <description>Thank you for your response. To clarify, we have purchased 2 Hadoop clusters: one for dev and test and the second for production. Each cluster will have 15 nodes (4 master, 9 worker, and 2 edge).&lt;BR /&gt;My background is in Oracle, so I need further clarification on how to architect the Hadoop environment. (It is my understanding that in Hadoop, a "database namespace" is synonymous with "schema owner" in Oracle)&lt;BR /&gt;We current have three Oracle databases: dwdev, dwtst, and dwprd and they are each on their own hardware server.&lt;BR /&gt;Within each database, there is a schema owner named marketing which owns a set of tables, ie. customer_master, product_master, etc.&lt;BR /&gt;If we want to simulate this in Hadoop, except that dev and test will exist on the same hardware cluster, how do we do that given that we do not want to change the existing schema owner and table names? So, in oracle, you have .,. Does this require having separate metastores?&lt;BR /&gt;</description>
    <pubDate>Wed, 02 Aug 2017 14:23:02 GMT</pubDate>
    <dc:creator>kjfischer</dc:creator>
    <dc:date>2017-08-02T14:23:02Z</dc:date>
  </channel>
</rss>

