[
https://issues.apache.org/jira/browse/HAWQ-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goden Yao updated HAWQ-422:
---------------------------
Fix Version/s: backlog
> All config paths are hardcoded
> ------------------------------
>
> Key: HAWQ-422
> URL: https://issues.apache.org/jira/browse/HAWQ-422
> Project: Apache HAWQ
> Issue Type: Bug
> Components: Command Line Tools
> Affects Versions: 2.0.0.0-incubating
> Reporter: Konstantin Boudnik
> Assignee: Radar Lei
> Fix For: backlog
>
>
> Looking through the python scripts, I see a common pattern of referring to
> configuration files via {{"%s/etc/hawq-site.xml" % GPHOME}} (see also
> HAWQ-421)
> This effectively hard-codes the location of configuration files relative to
> the location of hawq binaries. In Linux, applications and services are
> normally have their configs under {{/etc/service-name}} or similar.
> At any rate, it would be better to use {{HAWQ_CONF_DIR}} as the location of
> configuration files and expect it to be set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
