You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Goden Yao (JIRA)" <ji...@apache.org> on 2016/07/14 18:33:20 UTC
[jira] [Reopened] (HAWQ-456) Defaults file name is hardcoded
[ https://issues.apache.org/jira/browse/HAWQ-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Goden Yao reopened HAWQ-456:
----------------------------
reopen to update version
> Defaults file name is hardcoded
> -------------------------------
>
> Key: HAWQ-456
> URL: https://issues.apache.org/jira/browse/HAWQ-456
> Project: Apache HAWQ
> Issue Type: Bug
> Reporter: Konstantin Boudnik
> Assignee: Radar Lei
>
> Looking through the {{bin/}} scripts, I see a common pattern of referring to file, providing system defaults, as {{$GPHOME/greenplum_path.sh}} (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)