You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Lei Chang (JIRA)" <ji...@apache.org> on 2016/02/19 10:59:18 UTC

[jira] [Updated] (HAWQ-422) All config paths are hardcoded

     [ https://issues.apache.org/jira/browse/HAWQ-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lei Chang updated HAWQ-422:
---------------------------
    Assignee: Radar Lei  (was: Lei Chang)

> All config paths are hardcoded
> ------------------------------
>
>                 Key: HAWQ-422
>                 URL: https://issues.apache.org/jira/browse/HAWQ-422
>             Project: Apache HAWQ
>          Issue Type: Bug
>            Reporter: Konstantin Boudnik
>            Assignee: Radar Lei
>
> 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)