[
https://issues.apache.org/jira/browse/ATLAS-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16148009#comment-16148009
]
Sarath Subramanian commented on ATLAS-2087:
-------------------------------------------
[~rding], the UTs still fail after the patch ATLAS-2087.addendum.patch.
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/41/console
> Allow Atlas server to bind on a specific address
> ------------------------------------------------
>
> Key: ATLAS-2087
> URL: https://issues.apache.org/jira/browse/ATLAS-2087
> Project: Atlas
> Issue Type: Improvement
> Components: atlas-core
> Affects Versions: 0.8-incubating
> Reporter: Richard Ding
> Assignee: Richard Ding
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2087.2.patch, ATLAS-2087.addendum.patch,
> ATLAS-2087.patch
>
>
> Atlas server always bind to address "0.0.0.0":
> {code}
> connector.setHost("0.0.0.0");
> {code}
> But in many cases, user want to only run Atlas on a specified IP address
> (e.g. private network).
> The existing property "_atlas.server.bind.address_" should be used:
> {code}
> final String addr = conf.get("atlas.server.bind.address", "0.0.0.0");
> connector.setHost(addr);
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
