[ 
https://issues.apache.org/jira/browse/OODT-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16373959#comment-16373959
 ] 

ASF GitHub Bot commented on OODT-972:
-------------------------------------

Github user lewismc commented on the issue:

    https://github.com/apache/oodt/pull/56
  
    In addition to this, Radix generates the following filemgr.properties with 
incorrect paths
    ```
    org.apache.oodt.cas.filemgr.catalog.lucene.idxPath
    org.apache.oodt.cas.filemgr.repositorymgr.dirs
    org.apache.oodt.cas.filemgr.validation.dirs
    org.apache.oodt.cas.filemgr.mime.type.repository
    ```
    Say my SDS is deployed at ```/usr/local/coal-sds-deploy/```, Radix creates 
the default property values **less** the _filemgr_ directory e.g. 
```/usr/local/coal-sds-deploy/etc/mime-types.xml```. This is incorrect, the 
correct path should be 
```/usr/local/coal-sds-deploy/filemgr/etc/mime-types.xml```.
    I'll update the patch with this fix once we can agree on what to do with 
the above...


> Add filemgr.server and filemgr.client configuration keys to Radix 
> filemgr.properties
> ------------------------------------------------------------------------------------
>
>                 Key: OODT-972
>                 URL: https://issues.apache.org/jira/browse/OODT-972
>             Project: OODT
>          Issue Type: Improvement
>          Components: file manager, radix
>    Affects Versions: 1.2
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Major
>             Fix For: 1.2.1
>
>
> As per the [filemgr.propeerties included in the filemgr 
> tests|https://github.com/apache/oodt/blob/8a3d5194424d8327e8b3ffc4a2d45f18b56e3371/filemgr/src/test/resources/filemgr.properties#L18-L22]
>  we should augment the current Radix filemgr.proerties to offer the option 
> for a user to select the RPC mechanism for deploying a filemgr instance.
> Patch coming up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to