You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Shivram Mani (JIRA)" <ji...@apache.org> on 2017/11/02 17:59:07 UTC

[jira] [Resolved] (HAWQ-1541) PXF configs shouldn't be part of pxf webapp

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

Shivram Mani resolved HAWQ-1541.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0.0-incubating

> PXF configs shouldn't be part of pxf webapp
> -------------------------------------------
>
>                 Key: HAWQ-1541
>                 URL: https://issues.apache.org/jira/browse/HAWQ-1541
>             Project: Apache HAWQ
>          Issue Type: Improvement
>            Reporter: Shivram Mani
>            Assignee: Shivram Mani
>            Priority: Major
>             Fix For: 2.3.0.0-incubating
>
>
> The following config files are currently present as part of the pxf.war file under webapps/pxf/WEB-INF/classes/. 
> {code}
> pxf-log4j.properties         pxf-private.classpath        pxf-profiles-default.xml     pxf-profiles.xml             pxf-public.classpath
> {code}
> This conflicts with updates from the user in pxf/conf as the webapp picks the internal conf files when pxf restarts.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)