knox-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lmc...@apache.org
Subject svn commit: r1588707 - in /knox: site/books/knox-0-4-0/knox-0-4-0-new.html site/books/knox-0-4-0/knox-0-4-0.html trunk/books/0.4.0/book_gateway-details.md
Date Sat, 19 Apr 2014 21:12:18 GMT
Author: lmccay
Date: Sat Apr 19 21:12:17 2014
New Revision: 1588707

URL: http://svn.apache.org/r1588707
Log:
KNOX-327 clean up of gateway-details

Modified:
    knox/site/books/knox-0-4-0/knox-0-4-0-new.html
    knox/site/books/knox-0-4-0/knox-0-4-0.html
    knox/trunk/books/0.4.0/book_gateway-details.md

Modified: knox/site/books/knox-0-4-0/knox-0-4-0-new.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-4-0/knox-0-4-0-new.html?rev=1588707&r1=1588706&r2=1588707&view=diff
==============================================================================
--- knox/site/books/knox-0-4-0/knox-0-4-0-new.html (original)
+++ knox/site/books/knox-0-4-0/knox-0-4-0-new.html Sat Apr 19 21:12:17 2014
@@ -269,7 +269,7 @@ Server: Jetty(6.1.26)
   <li><a href="#Oozie+Examples">Oozie Examples</a></li>
   <li><a href="#HBase+Examples">HBase Examples</a></li>
   <li><a href="#Hive+Examples">Hive Examples</a></li>
-</ul></div><div id="Gateway+Details"><h2><a id="Gateway+Details"></a>Gateway
Details</h2><p>TODO</p><h3><a id="URL+Mapping"></a>URL
Mapping</h3><p>The gateway functions much like a reverse proxy. As such it maintains
a mapping of URLs that are exposed externally by the gateway to URLs that are provided by
the Hadoop cluster. Examples of mappings for the WebHDFS, WebHCat, Oozie and Stargate/HBase
are shown below. These mapping are generated from the combination of the gateway configuration
file (i.e. <code>{GATEWAY_HOME}/conf/gateway-site.xml</code>) and the cluster
topology descriptors (e.g. <code>{GATEWAY_HOME}/deployments/{cluster-name}.xml</code>).
The port numbers show for the Cluster URLs represent the default ports for these services.
The actual port number may be different for a given cluster.</p>
+</ul></div><div id="Gateway+Details"><h2><a id="Gateway+Details"></a>Gateway
Details</h2><h3><a id="URL+Mapping"></a>URL Mapping</h3><p>The
gateway functions much like a reverse proxy. As such it maintains a mapping of URLs that are
exposed externally by the gateway to URLs that are provided by the Hadoop cluster. Examples
of mappings for the WebHDFS, WebHCat, Oozie and Stargate/HBase are shown below. These mapping
are generated from the combination of the gateway configuration file (i.e. <code>{GATEWAY_HOME}/conf/gateway-site.xml</code>)
and the cluster topology descriptors (e.g. <code>{GATEWAY_HOME}/conf/topologies/{cluster-name}.xml</code>).
The port numbers show for the Cluster URLs represent the default ports for these services.
The actual port number may be different for a given cluster.</p>
 <ul>
   <li>WebHDFS
   <ul>
@@ -296,7 +296,7 @@ Server: Jetty(6.1.26)
     <li>Gateway: <code>jdbc:hive2://{gateway-host}:{gateway-port}/;ssl=true;sslTrustStore={gateway-trust-store-path};trustStorePassword={gateway-trust-store-password}?hive.server2.transport.mode=http;hive.server2.thrift.http.path={gateway-path}/{cluster-name}/hive</code></li>
     <li>Cluster: <code>http://{hive-host}:10001/cliservice</code></li>
   </ul></li>
-</ul><p>The values for <code>{gateway-host}</code>, <code>{gateway-port}</code>,
<code>{gateway-path}</code> are provided via the gateway configuration file (i.e.
<code>{GATEWAY_HOME}/conf/gateway-site.xml</code>).</p><p>The value
for <code>{cluster-name}</code> is derived from the file name of the cluster topology
descriptor (e.g. <code>{GATEWAY_HOME}/deployments/{cluster-name}.xml</code>).</p><p>The
value for <code>{webhdfs-host}</code>, <code>{webhcat-host}</code>,
<code>{oozie-host}</code>, <code>{hbase-host}</code> and <code>{hive-host}</code>
are provided via the cluster topology descriptor (e.g. <code>{GATEWAY_HOME}/deployments/{cluster-name}.xml</code>).</p><p>Note:
The ports 50070, 50111, 11000, 60080 and 10001 are the defaults for WebHDFS, WebHCat, Oozie,
Stargate/HBase and Hive respectively. Their values can also be provided via the cluster topology
descriptor if your Hadoop cluster uses different ports.</p></div><div id="Configuration"><h3><a
id="Configuration"></a>Confi
 guration</h3><h4><a id="Topology+Descriptors"></a>Topology Descriptors</h4><p>The
topology descriptor files provide the gateway with per-cluster configuration information.
This includes configuration for both the providers within the gateway and the services within
the Hadoop cluster. These files are located in <code>{GATEWAY_HOME}/deployments</code>.
The general outline of this document looks like this.</p>
+</ul><p>The values for <code>{gateway-host}</code>, <code>{gateway-port}</code>,
<code>{gateway-path}</code> are provided via the gateway configuration file (i.e.
<code>{GATEWAY_HOME}/conf/gateway-site.xml</code>).</p><p>The value
for <code>{cluster-name}</code> is derived from the file name of the cluster topology
descriptor (e.g. <code>{GATEWAY_HOME}/deployments/{cluster-name}.xml</code>).</p><p>The
value for <code>{webhdfs-host}</code>, <code>{webhcat-host}</code>,
<code>{oozie-host}</code>, <code>{hbase-host}</code> and <code>{hive-host}</code>
are provided via the cluster topology descriptor (e.g. <code>{GATEWAY_HOME}/deployments/{cluster-name}.xml</code>).</p><p>Note:
The ports 50070, 50111, 11000, 60080 (default 8080) and 10001 are the defaults for WebHDFS,
WebHCat, Oozie, Stargate/HBase and Hive respectively. Their values can also be provided via
the cluster topology descriptor if your Hadoop cluster uses different ports.</p></div><div
id="Configuration"><h3><a id="Configura
 tion"></a>Configuration</h3><h4><a id="Topology+Descriptors"></a>Topology
Descriptors</h4><p>The topology descriptor files provide the gateway with per-cluster
configuration information. This includes configuration for both the providers within the gateway
and the services within the Hadoop cluster. These files are located in <code>{GATEWAY_HOME}/deployments</code>.
The general outline of this document looks like this.</p>
 <pre><code>&lt;topology&gt;
     &lt;gateway&gt;
         &lt;provider&gt;

Modified: knox/site/books/knox-0-4-0/knox-0-4-0.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-4-0/knox-0-4-0.html?rev=1588707&r1=1588706&r2=1588707&view=diff
==============================================================================
--- knox/site/books/knox-0-4-0/knox-0-4-0.html (original)
+++ knox/site/books/knox-0-4-0/knox-0-4-0.html Sat Apr 19 21:12:17 2014
@@ -269,7 +269,7 @@ Server: Jetty(6.1.26)
   <li><a href="#Oozie+Examples">Oozie Examples</a></li>
   <li><a href="#HBase+Examples">HBase Examples</a></li>
   <li><a href="#Hive+Examples">Hive Examples</a></li>
-</ul><h2><a id="Gateway+Details"></a>Gateway Details</h2><p>TODO</p><h3><a
id="URL+Mapping"></a>URL Mapping</h3><p>The gateway functions much like
a reverse proxy. As such it maintains a mapping of URLs that are exposed externally by the
gateway to URLs that are provided by the Hadoop cluster. Examples of mappings for the WebHDFS,
WebHCat, Oozie and Stargate/HBase are shown below. These mapping are generated from the combination
of the gateway configuration file (i.e. <code>{GATEWAY_HOME}/conf/gateway-site.xml</code>)
and the cluster topology descriptors (e.g. <code>{GATEWAY_HOME}/deployments/{cluster-name}.xml</code>).
The port numbers show for the Cluster URLs represent the default ports for these services.
The actual port number may be different for a given cluster.</p>
+</ul><h2><a id="Gateway+Details"></a>Gateway Details</h2><h3><a
id="URL+Mapping"></a>URL Mapping</h3><p>The gateway functions much like
a reverse proxy. As such it maintains a mapping of URLs that are exposed externally by the
gateway to URLs that are provided by the Hadoop cluster. Examples of mappings for the WebHDFS,
WebHCat, Oozie and Stargate/HBase are shown below. These mapping are generated from the combination
of the gateway configuration file (i.e. <code>{GATEWAY_HOME}/conf/gateway-site.xml</code>)
and the cluster topology descriptors (e.g. <code>{GATEWAY_HOME}/conf/topologies/{cluster-name}.xml</code>).
The port numbers show for the Cluster URLs represent the default ports for these services.
The actual port number may be different for a given cluster.</p>
 <ul>
   <li>WebHDFS
   <ul>
@@ -296,7 +296,7 @@ Server: Jetty(6.1.26)
     <li>Gateway: <code>jdbc:hive2://{gateway-host}:{gateway-port}/;ssl=true;sslTrustStore={gateway-trust-store-path};trustStorePassword={gateway-trust-store-password}?hive.server2.transport.mode=http;hive.server2.thrift.http.path={gateway-path}/{cluster-name}/hive</code></li>
     <li>Cluster: <code>http://{hive-host}:10001/cliservice</code></li>
   </ul></li>
-</ul><p>The values for <code>{gateway-host}</code>, <code>{gateway-port}</code>,
<code>{gateway-path}</code> are provided via the gateway configuration file (i.e.
<code>{GATEWAY_HOME}/conf/gateway-site.xml</code>).</p><p>The value
for <code>{cluster-name}</code> is derived from the file name of the cluster topology
descriptor (e.g. <code>{GATEWAY_HOME}/deployments/{cluster-name}.xml</code>).</p><p>The
value for <code>{webhdfs-host}</code>, <code>{webhcat-host}</code>,
<code>{oozie-host}</code>, <code>{hbase-host}</code> and <code>{hive-host}</code>
are provided via the cluster topology descriptor (e.g. <code>{GATEWAY_HOME}/deployments/{cluster-name}.xml</code>).</p><p>Note:
The ports 50070, 50111, 11000, 60080 and 10001 are the defaults for WebHDFS, WebHCat, Oozie,
Stargate/HBase and Hive respectively. Their values can also be provided via the cluster topology
descriptor if your Hadoop cluster uses different ports.</p><h3><a id="Configuration"></a>Configuration</h3><h4><a
id="Topolo
 gy+Descriptors"></a>Topology Descriptors</h4><p>The topology descriptor
files provide the gateway with per-cluster configuration information. This includes configuration
for both the providers within the gateway and the services within the Hadoop cluster. These
files are located in <code>{GATEWAY_HOME}/deployments</code>. The general outline
of this document looks like this.</p>
+</ul><p>The values for <code>{gateway-host}</code>, <code>{gateway-port}</code>,
<code>{gateway-path}</code> are provided via the gateway configuration file (i.e.
<code>{GATEWAY_HOME}/conf/gateway-site.xml</code>).</p><p>The value
for <code>{cluster-name}</code> is derived from the file name of the cluster topology
descriptor (e.g. <code>{GATEWAY_HOME}/deployments/{cluster-name}.xml</code>).</p><p>The
value for <code>{webhdfs-host}</code>, <code>{webhcat-host}</code>,
<code>{oozie-host}</code>, <code>{hbase-host}</code> and <code>{hive-host}</code>
are provided via the cluster topology descriptor (e.g. <code>{GATEWAY_HOME}/deployments/{cluster-name}.xml</code>).</p><p>Note:
The ports 50070, 50111, 11000, 60080 (default 8080) and 10001 are the defaults for WebHDFS,
WebHCat, Oozie, Stargate/HBase and Hive respectively. Their values can also be provided via
the cluster topology descriptor if your Hadoop cluster uses different ports.</p><h3><a
id="Configuration"></a>Configuration</h3><h
 4><a id="Topology+Descriptors"></a>Topology Descriptors</h4><p>The
topology descriptor files provide the gateway with per-cluster configuration information.
This includes configuration for both the providers within the gateway and the services within
the Hadoop cluster. These files are located in <code>{GATEWAY_HOME}/deployments</code>.
The general outline of this document looks like this.</p>
 <pre><code>&lt;topology&gt;
     &lt;gateway&gt;
         &lt;provider&gt;

Modified: knox/trunk/books/0.4.0/book_gateway-details.md
URL: http://svn.apache.org/viewvc/knox/trunk/books/0.4.0/book_gateway-details.md?rev=1588707&r1=1588706&r2=1588707&view=diff
==============================================================================
--- knox/trunk/books/0.4.0/book_gateway-details.md (original)
+++ knox/trunk/books/0.4.0/book_gateway-details.md Sat Apr 19 21:12:17 2014
@@ -17,14 +17,13 @@
 
 ## Gateway Details ##
 
-TODO
 
 ### URL Mapping ###
 
 The gateway functions much like a reverse proxy.
 As such it maintains a mapping of URLs that are exposed externally by the gateway to URLs
that are provided by the Hadoop cluster.
 Examples of mappings for the WebHDFS, WebHCat, Oozie and Stargate/HBase are shown below.
-These mapping are generated from the combination of the gateway configuration file (i.e.
`{GATEWAY_HOME}/conf/gateway-site.xml`) and the cluster topology descriptors (e.g. `{GATEWAY_HOME}/deployments/{cluster-name}.xml`).
+These mapping are generated from the combination of the gateway configuration file (i.e.
`{GATEWAY_HOME}/conf/gateway-site.xml`) and the cluster topology descriptors (e.g. `{GATEWAY_HOME}/conf/topologies/{cluster-name}.xml`).
 The port numbers show for the Cluster URLs represent the default ports for these services.
 The actual port number may be different for a given cluster.
 
@@ -50,7 +49,7 @@ The value for `{cluster-name}` is derive
 
 The value for `{webhdfs-host}`, `{webhcat-host}`, `{oozie-host}`, `{hbase-host}` and `{hive-host}`
are provided via the cluster topology descriptor (e.g. `{GATEWAY_HOME}/deployments/{cluster-name}.xml`).
 
-Note: The ports 50070, 50111, 11000, 60080 and 10001 are the defaults for WebHDFS, WebHCat,
Oozie, Stargate/HBase and Hive respectively.
+Note: The ports 50070, 50111, 11000, 60080 (default 8080) and 10001 are the defaults for
WebHDFS, WebHCat, Oozie, Stargate/HBase and Hive respectively.
 Their values can also be provided via the cluster topology descriptor if your Hadoop cluster
uses different ports.
 
 <<config.md>>



Mime
View raw message