THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Status
Current state: In-progressComplete
Discussion thread:
JIRA:
Jira | ||||||
---|---|---|---|---|---|---|
|
...
This would provide interesting possibilities for existing hadoop cli's.
Architecture
The following is the startup sequence diagram for this feature. Changes are highlighted in blue.
Configuration
Configuration for this feature will be in gateway-site.xml config file.
Following are the settings relevant to this feature
- The property gateway.port.mapping.enabled is used to turn feature ON/OFF.
- The property gateway.port.mapping.{topologyName} and it value {port} maps {topologyName} to {port}.
Example:
Code Block |
---|
<!-- Optional, true by default-->
<property>
<name>gateway.port.mapping.enabled</name>
<value>true</value>
<description>Enable/Disable gateway topology port mapping feature.</description>
</property>
<!-- Multi Port Gateway -->
<property>
<name>gateway.port.mapping.eerie</name>
<value>5443</value>
<description>The HTTP port for the Gateway.</description>
</property>
<property>
<name>gateway.port.mapping.huron</name>
<value>6443</value>
<description>The HTTP port for the Gateway.</description>
</property>
<property>
<name>gateway.port.mapping.ontario</name>
<value>7443</value>
<description>The HTTP port for the Gateway.</description>
</property> |
Improvements
- Need to address the inability for the hadoop java client to deal with spnego challenges from the DN redirect.
...