[jira] [Commented] (OODT-972) Add filemgr.server and filemgr.client configuration keys to Radix filemgr.properties

2018-02-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on OODT-972:
-

Github user lewismc commented on the issue:

https://github.com/apache/oodt/pull/56
  
There also appears to be a bug in the auto-generated product-types.xml as 
follows; instead of 
```

```
Note above correct protocol assignment ```file:///```, the file is instead 
written as
```

```
Note two forward slashes instead of three!


> 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)


[jira] [Commented] (OODT-972) Add filemgr.server and filemgr.client configuration keys to Radix filemgr.properties

2018-02-22 Thread ASF GitHub Bot (JIRA)

[ 
https://issues.apache.org/jira/browse/OODT-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)


[jira] [Commented] (OODT-972) Add filemgr.server and filemgr.client configuration keys to Radix filemgr.properties

2018-02-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on OODT-972:
-

Github user lewismc commented on the issue:

https://github.com/apache/oodt/pull/56
  
Or of course, we could avoid this patch and just make sure that the Radix 
filemgr.properties is in sync with the [default filemgr 
one](https://github.com/apache/oodt/blob/8a3d5194424d8327e8b3ffc4a2d45f18b56e3371/filemgr/src/main/resources/filemgr.properties)!


> 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)


[jira] [Commented] (OODT-972) Add filemgr.server and filemgr.client configuration keys to Radix filemgr.properties

2018-02-22 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on OODT-972:
-

Github user lewismc commented on the issue:

https://github.com/apache/oodt/pull/56
  
One issue I do have however, should we be making the AvroRPC default moving 
forward?


> 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)


[jira] [Created] (OODT-971) Default filemgr.properties is buggy in radix post AvroRPC

2018-02-22 Thread Lewis John McGibbney (JIRA)
Lewis John McGibbney created OODT-971:
-

 Summary: Default filemgr.properties is buggy in radix post AvroRPC
 Key: OODT-971
 URL: https://issues.apache.org/jira/browse/OODT-971
 Project: OODT
  Issue Type: Bug
  Components: file manager, radix
Affects Versions: 1.2
Reporter: Lewis John McGibbney
Assignee: Lewis John McGibbney
 Fix For: 1.2.1


When a user creates and builds a new Radix distribution, the filemgr.properties 
references such as 
{code}
# xml rpc client configuration
org.apache.oodt.cas.filemgr.system.xmlrpc.connectionTimeout.minutes=20
org.apache.oodt.cas.filemgr.system.xmlrpc.requestTimeout.minutes=60
#org.apache.oodt.cas.filemgr.system.xmlrpc.connection.retries=0
#org.apache.oodt.cas.filemgr.system.xmlrpc.connection.retry.interval.seconds=3
{code}
Although these are _fine_ e.g. they still work, the package naming is now off 
as there is no package actually named 
{code}
org.apache.oodt.cas.filemgr.system.xmlrpc...
{code}
The only issue I have with changing this important configuration setting, is 
that is would essentially be backwards non-compatible with EVERY OODT install 
unless your new install was powered by Radix.

Any comments as to what to do? I am happy to close this as *wont fix* due to 
the backwards non-compatible nature of a proposed fix which would _correct_ the 
package naming but I just wanted to post for consideration here folks. I will 
open a new issue regarding adding AvroRPC filemgr configuration in a separate 
issue.



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