[jira] [Commented] (OODT-976) Upgrade Apache Tika to 1.18

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-976:
-

Github user lewismc commented on the issue:

https://github.com/apache/oodt/pull/61
  
> ...I am not sure we need to rename it since I believe it is explicitly 
identified in the bin/filemgr script as an argument or system property, e.g., 
here. 

ACK

> ...Also can you submit a pull request in Tika to fix the location of the 
freedesktop wiki?

Yes will do it at lunch thanks.


> Upgrade Apache Tika to 1.18
> ---
>
> Key: OODT-976
> URL: https://issues.apache.org/jira/browse/OODT-976
> Project: OODT
>  Issue Type: Improvement
>  Components: core, file manager, radix
>Affects Versions: 1.2.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.9
>
>
> tika-core and tika-parsers 1.13 dependencies are pretty outdated now. Tika 
> 1.18 is available so we should upgrade.



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

[jira] [Commented] (OODT-976) Upgrade Apache Tika to 1.18

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-976:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/61
  
@lewismc great question. I am not sure we need to rename it since I believe 
it is explicitly identified in the bin/filemgr script as an argument or system 
property, e.g., 
[here](https://github.com/apache/oodt/blob/master/filemgr/src/main/resources/filemgr.properties#L137).
 Also can you submit a pull request in Tika to fix the location of the 
freedesktop wiki?


> Upgrade Apache Tika to 1.18
> ---
>
> Key: OODT-976
> URL: https://issues.apache.org/jira/browse/OODT-976
> Project: OODT
>  Issue Type: Improvement
>  Components: core, file manager, radix
>Affects Versions: 1.2.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.9
>
>
> tika-core and tika-parsers 1.13 dependencies are pretty outdated now. Tika 
> 1.18 is available so we should upgrade.



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

[jira] [Commented] (OODT-976) Upgrade Apache Tika to 1.18

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-976:
-

Github user lewismc commented on the issue:

https://github.com/apache/oodt/pull/61
  
Hi @chrismattmann I'm testing with DRAT... quick question though. Is it 
necessary for us to rename the ```mime-types.xml``` files present in OODT (and 
updated as part of the PR) to the Tika equivalent e.g. 
[tika-mimetypes.xml](https://github.com/apache/tika/blob/70ca280f11fe4127df290b8027c6bc1d5180271f/tika-core/src/main/resources/org/apache/tika/mime/tika-mimetypes.xml)?
 It looks like the [freedesktop.org link at presented in 
MimeTypesReader.java](https://github.com/apache/tika/blob/70ca280f11fe4127df290b8027c6bc1d5180271f/tika-core/src/main/java/org/apache/tika/mime/MimeTypesReader.java#L99)
 is broken as well...


> Upgrade Apache Tika to 1.18
> ---
>
> Key: OODT-976
> URL: https://issues.apache.org/jira/browse/OODT-976
> Project: OODT
>  Issue Type: Improvement
>  Components: core, file manager, radix
>Affects Versions: 1.2.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.9
>
>
> tika-core and tika-parsers 1.13 dependencies are pretty outdated now. Tika 
> 1.18 is available so we should upgrade.



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

[jira] [Commented] (OODT-975) Upgrade Tomcat in radix

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-975:
-

Github user lewismc commented on the issue:

https://github.com/apache/oodt/pull/60
  
Would like to upgrade by EoD today unless there are other comments folks. 
Thanks.


> Upgrade Tomcat in radix
> ---
>
> Key: OODT-975
> URL: https://issues.apache.org/jira/browse/OODT-975
> Project: OODT
>  Issue Type: Improvement
>  Components: radix
>Affects Versions: 1.2.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Minor
> Fix For: 1.9
>
>
> Tomcat is sitting at 5.X prior to org.apache.tomcat package renaming. This 
> issue will make the upgrade to the most recent Tomcat version... which I 
> assume will also improve security for radix installations. 



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

[jira] [Commented] (OODT-975) Upgrade Tomcat in radix

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-975:
-

Github user lewismc commented on the issue:

https://github.com/apache/oodt/pull/60
  
Also, my tests with COAL-SDS mimic the behaviour with DRAT e.g. the upgrade 
is working.


> Upgrade Tomcat in radix
> ---
>
> Key: OODT-975
> URL: https://issues.apache.org/jira/browse/OODT-975
> Project: OODT
>  Issue Type: Improvement
>  Components: radix
>Affects Versions: 1.2.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Minor
> Fix For: 1.9
>
>
> Tomcat is sitting at 5.X prior to org.apache.tomcat package renaming. This 
> issue will make the upgrade to the most recent Tomcat version... which I 
> assume will also improve security for radix installations. 



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

[jira] [Commented] (OODT-975) Upgrade Tomcat in radix

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-975:
-

Github user lewismc commented on the issue:

https://github.com/apache/oodt/pull/60
  
@chrismattmann at some stage in the past, the Tomcat dependency in [DRAT's 
distribution 
pom.xml](https://github.com/apache/drat/blob/master/distribution/pom.xml#L18) 
has been manually upgraded as this is much more recent than the version 
packaged as part of vanilla radix archetype. I did however make a manual Tomcat 
upgrade in the DRAT source code (PR available at 
https://github.com/apache/drat/pull/124) along with an OODT upgrade to 1.2.2. 
All tests looks good and my screenshots substantiate that.


> Upgrade Tomcat in radix
> ---
>
> Key: OODT-975
> URL: https://issues.apache.org/jira/browse/OODT-975
> Project: OODT
>  Issue Type: Improvement
>  Components: radix
>Affects Versions: 1.2.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Minor
> Fix For: 1.9
>
>
> Tomcat is sitting at 5.X prior to org.apache.tomcat package renaming. This 
> issue will make the upgrade to the most recent Tomcat version... which I 
> assume will also improve security for radix installations. 



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

[jira] [Commented] (OODT-975) Upgrade Tomcat in radix

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-975:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/60
  
@lewismc can you please test with DRAT?


> Upgrade Tomcat in radix
> ---
>
> Key: OODT-975
> URL: https://issues.apache.org/jira/browse/OODT-975
> Project: OODT
>  Issue Type: Improvement
>  Components: radix
>Affects Versions: 1.2.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Minor
> Fix For: 1.9
>
>
> Tomcat is sitting at 5.X prior to org.apache.tomcat package renaming. This 
> issue will make the upgrade to the most recent Tomcat version... which I 
> assume will also improve security for radix installations. 



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

[jira] [Commented] (OODT-976) Upgrade Apache Tika to 1.18

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-976:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/61
  
@lewismc can you test with DRAT? my worry is that some of our unit tests 
miss the full end to end coverage of DRAT.


> Upgrade Apache Tika to 1.18
> ---
>
> Key: OODT-976
> URL: https://issues.apache.org/jira/browse/OODT-976
> Project: OODT
>  Issue Type: Improvement
>  Components: core, file manager, radix
>Affects Versions: 1.2.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.9
>
>
> tika-core and tika-parsers 1.13 dependencies are pretty outdated now. Tika 
> 1.18 is available so we should upgrade.



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

[jira] [Commented] (OODT-976) Upgrade Apache Tika to 1.18

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-976:
-

GitHub user lewismc opened a pull request:

https://github.com/apache/oodt/pull/61

OODT-976 Upgrade Apache Tika to 1.18

This PR addresses https://issues.apache.org/jira/browse/OODT-976
It turns out that commons-compress also needed updating. All tests pass 
locally. 
The Tika 1.18 mime-types.xml file has been copied to every instance of it 
within OODT.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lewismc/oodt OODT-976

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/61.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #61


commit f0de761c1e0d9e487824d2d2247a02f601e36d74
Author: Lewis John McGibbney 
Date:   2018-04-25T06:21:21Z

OODT-976 Upgrade Apache Tika to 1.18




> Upgrade Apache Tika to 1.18
> ---
>
> Key: OODT-976
> URL: https://issues.apache.org/jira/browse/OODT-976
> Project: OODT
>  Issue Type: Improvement
>  Components: core, file manager, radix
>Affects Versions: 1.2.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.9
>
>
> tika-core and tika-parsers 1.13 dependencies are pretty outdated now. Tika 
> 1.18 is available so we should upgrade.



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

[jira] [Commented] (OODT-975) Upgrade Tomcat in radix

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-975:
-

GitHub user lewismc opened a pull request:

https://github.com/apache/oodt/pull/60

OODT-975 Upgrade Tomcat in radix

This issue addresses https://issues.apache.org/jira/browse/OODT-975

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lewismc/oodt OODT-975

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/60.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #60


commit 40ed14e48510b9e6993caaa97c7d69bad9ff99a7
Author: Lewis John McGibbney 
Date:   2018-04-24T21:51:10Z

OODT-975 Upgrade Tomcat in radix




> Upgrade Tomcat in radix
> ---
>
> Key: OODT-975
> URL: https://issues.apache.org/jira/browse/OODT-975
> Project: OODT
>  Issue Type: Improvement
>  Components: radix
>Affects Versions: 1.2.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Minor
> Fix For: 1.9
>
>
> Tomcat is sitting at 5.X prior to org.apache.tomcat package renaming. This 
> issue will make the upgrade to the most recent Tomcat version... which I 
> assume will also improve security for radix installations. 



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

[jira] [Commented] (OODT-973) Update mvn/archetypes/radix module script templates to remove ghost PID files

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-973:
-

Github user ThejanW commented on the issue:

https://github.com/apache/oodt/pull/58
  
thanks for the merge @chrismattmann 


> Update mvn/archetypes/radix module script templates to remove ghost PID files
> -
>
> Key: OODT-973
> URL: https://issues.apache.org/jira/browse/OODT-973
> Project: OODT
>  Issue Type: Bug
>  Components: radix
>Affects Versions: 1.2.2
>Reporter: Thejan Wijesinghe
>Assignee: Chris A. Mattmann
>Priority: Minor
> Fix For: 1.9
>
>
> In mvn/archetypes/radix module script templates, OODT stop process does not 
> properly delete the PID files $WORKFLOW_PID & $RESMGR_PID, even when there 
> are no matching processes to those related PIDs. Therefore workflow manager 
> and resource manager sometime fails to start again.



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

[jira] [Commented] (OODT-973) Update mvn/archetypes/radix module script templates to remove ghost PID files

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-973:
-

Github user asfgit closed the pull request at:

https://github.com/apache/oodt/pull/58


> Update mvn/archetypes/radix module script templates to remove ghost PID files
> -
>
> Key: OODT-973
> URL: https://issues.apache.org/jira/browse/OODT-973
> Project: OODT
>  Issue Type: Bug
>  Components: radix
>Affects Versions: 1.2.2
>Reporter: Thejan Wijesinghe
>Assignee: Chris A. Mattmann
>Priority: Minor
> Fix For: 1.9
>
>
> In mvn/archetypes/radix module script templates, OODT stop process does not 
> properly delete the PID files $WORKFLOW_PID & $RESMGR_PID, even when there 
> are no matching processes to those related PIDs. Therefore workflow manager 
> and resource manager sometime fails to start again.



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

[jira] [Commented] (OODT-966) agility broken syntax under Python 3.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-966:
-

Github user lewismc commented on the issue:

https://github.com/apache/oodt/pull/54
  
Yep, I have the branch locally so will make an attempt to revisit it 
reasonably soon.


> agility broken syntax under Python 3.X
> --
>
> Key: OODT-966
> URL: https://issues.apache.org/jira/browse/OODT-966
> Project: OODT
>  Issue Type: Bug
>  Components: agility
>Affects Versions: 1.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 1.9
>
>
> Using OODT master branch, python setup.py install results in the following
> {code}
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py to 
> webgrid.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py", line 51
> except Exception, e:
> ^
> SyntaxError: invalid syntax
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py to 
> workflow.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py", line 129
> print 'available events:', events
> ^
> SyntaxError: Missing parentheses in call to 'print'
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/xmlutils.py to 
> xmlutils.cpython-36.pyc
> creating build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/PKG-INFO -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/SOURCES.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/dependency_links.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/entry_points.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/namespace_packages.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/top_level.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/zip-safe -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> creating dist
> creating 'dist/oodt-1.2.dev_r0-py3.6.egg' and adding 
> 'build/bdist.macosx-10.7-x86_64/egg' to it
> removing 'build/bdist.macosx-10.7-x86_64/egg' (and everything under it)
> Processing oodt-1.2.dev_r0-py3.6.egg
> Copying oodt-1.2.dev_r0-py3.6.egg to 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages
> Adding oodt 1.2.dev-r0 to easy-install.pth file
> Installing webgrid script to /Users/lmcgibbn/miniconda3/bin
> Installed 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages/oodt-1.2.dev_r0-py3.6.egg
> Processing dependencies for oodt===1.2.dev-r0
> Finished processing dependencies for oodt===1.2.dev-r0
> {code}
> Fix coming up



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

[jira] [Commented] (OODT-966) agility broken syntax under Python 3.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-966:
-

Github user lewismc closed the pull request at:

https://github.com/apache/oodt/pull/54


> agility broken syntax under Python 3.X
> --
>
> Key: OODT-966
> URL: https://issues.apache.org/jira/browse/OODT-966
> Project: OODT
>  Issue Type: Bug
>  Components: agility
>Affects Versions: 1.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 1.9
>
>
> Using OODT master branch, python setup.py install results in the following
> {code}
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py to 
> webgrid.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py", line 51
> except Exception, e:
> ^
> SyntaxError: invalid syntax
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py to 
> workflow.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py", line 129
> print 'available events:', events
> ^
> SyntaxError: Missing parentheses in call to 'print'
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/xmlutils.py to 
> xmlutils.cpython-36.pyc
> creating build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/PKG-INFO -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/SOURCES.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/dependency_links.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/entry_points.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/namespace_packages.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/top_level.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/zip-safe -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> creating dist
> creating 'dist/oodt-1.2.dev_r0-py3.6.egg' and adding 
> 'build/bdist.macosx-10.7-x86_64/egg' to it
> removing 'build/bdist.macosx-10.7-x86_64/egg' (and everything under it)
> Processing oodt-1.2.dev_r0-py3.6.egg
> Copying oodt-1.2.dev_r0-py3.6.egg to 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages
> Adding oodt 1.2.dev-r0 to easy-install.pth file
> Installing webgrid script to /Users/lmcgibbn/miniconda3/bin
> Installed 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages/oodt-1.2.dev_r0-py3.6.egg
> Processing dependencies for oodt===1.2.dev-r0
> Finished processing dependencies for oodt===1.2.dev-r0
> {code}
> Fix coming up



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

[jira] [Commented] (OODT-966) agility broken syntax under Python 3.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-966:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/54
  
ack got it @lewismc is it ok then to close this and if you get time to fix 
the tests, open a new one?


> agility broken syntax under Python 3.X
> --
>
> Key: OODT-966
> URL: https://issues.apache.org/jira/browse/OODT-966
> Project: OODT
>  Issue Type: Bug
>  Components: agility
>Affects Versions: 1.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 1.9
>
>
> Using OODT master branch, python setup.py install results in the following
> {code}
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py to 
> webgrid.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py", line 51
> except Exception, e:
> ^
> SyntaxError: invalid syntax
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py to 
> workflow.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py", line 129
> print 'available events:', events
> ^
> SyntaxError: Missing parentheses in call to 'print'
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/xmlutils.py to 
> xmlutils.cpython-36.pyc
> creating build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/PKG-INFO -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/SOURCES.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/dependency_links.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/entry_points.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/namespace_packages.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/top_level.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/zip-safe -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> creating dist
> creating 'dist/oodt-1.2.dev_r0-py3.6.egg' and adding 
> 'build/bdist.macosx-10.7-x86_64/egg' to it
> removing 'build/bdist.macosx-10.7-x86_64/egg' (and everything under it)
> Processing oodt-1.2.dev_r0-py3.6.egg
> Copying oodt-1.2.dev_r0-py3.6.egg to 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages
> Adding oodt 1.2.dev-r0 to easy-install.pth file
> Installing webgrid script to /Users/lmcgibbn/miniconda3/bin
> Installed 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages/oodt-1.2.dev_r0-py3.6.egg
> Processing dependencies for oodt===1.2.dev-r0
> Finished processing dependencies for oodt===1.2.dev-r0
> {code}
> Fix coming up



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

[jira] [Commented] (OODT-966) agility broken syntax under Python 3.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-966:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/54
  
@lewismc do you have a full fix for this yet?


> agility broken syntax under Python 3.X
> --
>
> Key: OODT-966
> URL: https://issues.apache.org/jira/browse/OODT-966
> Project: OODT
>  Issue Type: Bug
>  Components: agility
>Affects Versions: 1.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 1.9
>
>
> Using OODT master branch, python setup.py install results in the following
> {code}
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py to 
> webgrid.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py", line 51
> except Exception, e:
> ^
> SyntaxError: invalid syntax
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py to 
> workflow.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py", line 129
> print 'available events:', events
> ^
> SyntaxError: Missing parentheses in call to 'print'
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/xmlutils.py to 
> xmlutils.cpython-36.pyc
> creating build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/PKG-INFO -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/SOURCES.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/dependency_links.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/entry_points.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/namespace_packages.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/top_level.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/zip-safe -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> creating dist
> creating 'dist/oodt-1.2.dev_r0-py3.6.egg' and adding 
> 'build/bdist.macosx-10.7-x86_64/egg' to it
> removing 'build/bdist.macosx-10.7-x86_64/egg' (and everything under it)
> Processing oodt-1.2.dev_r0-py3.6.egg
> Copying oodt-1.2.dev_r0-py3.6.egg to 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages
> Adding oodt 1.2.dev-r0 to easy-install.pth file
> Installing webgrid script to /Users/lmcgibbn/miniconda3/bin
> Installed 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages/oodt-1.2.dev_r0-py3.6.egg
> Processing dependencies for oodt===1.2.dev-r0
> Finished processing dependencies for oodt===1.2.dev-r0
> {code}
> Fix coming up



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

[jira] [Commented] (OODT-970) Netty Transceiver throws an NPE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-970:
-

Github user asfgit closed the pull request at:

https://github.com/apache/oodt/pull/55


> Netty Transceiver throws an NPE
> ---
>
> Key: OODT-970
> URL: https://issues.apache.org/jira/browse/OODT-970
> Project: OODT
>  Issue Type: Test
>  Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Chris A. Mattmann
>Priority: Major
> Fix For: 1.9
>
>
> Netty transceiver throws an NPE whenever the Avro File Manager client is 
> called after the first time. 
> {code:java}
> java.lang.NullPointerException: null
> ! at 
> org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:431)
> ! at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
> ! at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> ! at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:181)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
> ! at 
> org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:84)
> {code}
> Cause is: transceiver being closed after every use inside finally{} block.



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

[jira] [Commented] (OODT-970) Netty Transceiver throws an NPE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-970:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/55
  
awesome thanks @IMS94 OK so build passes on `apache:development` branch. 
Going to merge into `apache:master` and then push. Thanks!

```
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ oodt ---
[INFO] Installing /Users/mattmann/git/oodt/pom.xml to 
/Users/mattmann/.m2/repository/org/apache/oodt/oodt/1.9-SNAPSHOT/oodt-1.9-SNAPSHOT.pom
[INFO] 

[INFO] Reactor Summary:
[INFO] 
[INFO] OODT Core .. SUCCESS [  
2.508 s]
[INFO] Common Utilities ... SUCCESS [ 
30.655 s]
[INFO] CAS Command Line Interface . SUCCESS [ 
10.708 s]
[INFO] OODT - Configuration Management  SUCCESS [ 
25.957 s]
[INFO] Process Control System Input Data Package .. SUCCESS [  
4.017 s]
[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container 
SUCCESS [  6.097 s]
[INFO] Catalog and Archive File Management Component .. SUCCESS [03:50 
min]
[INFO] Catalog and Archive Resource Management Component .. SUCCESS [ 
28.565 s]
[INFO] Catalog and Archive Workflow Management Component .. SUCCESS [ 
38.392 s]
[INFO] Catalog and Archive Crawling Framework . SUCCESS [ 
24.234 s]
[INFO] OODT CAS Curator Single Sign On Security Package ... SUCCESS [  
1.885 s]
[INFO] CAS Curation Web Services .. SUCCESS [ 
10.409 s]
[INFO] Process Control System Core Package  SUCCESS [ 
19.409 s]
[INFO] OODT Wicket Web Components . SUCCESS [  
5.704 s]
[INFO] CAS Curation Interface . SUCCESS [ 
11.966 s]
[INFO] CAS PGE Adaptor Framework .. SUCCESS [ 
26.062 s]
[INFO] CAS Installer Maven Mojo ... SUCCESS [  
3.811 s]
[INFO] OODT :: Archetypes :: OpsUI  SUCCESS [  
1.136 s]
[INFO] OODT :: Archetypes :: RADiX  SUCCESS [  
1.382 s]
[INFO] OODT :: Archetypes . SUCCESS [  
0.054 s]
[INFO] CAS File Manager Browser Web App ... SUCCESS [  
9.862 s]
[INFO] CAS Workflow Manager Monitor Web App ... SUCCESS [  
5.577 s]
[INFO] CAS Product Server Web Application . SUCCESS [ 
17.040 s]
[INFO] CAS Workflow REST Services . SUCCESS [  
4.005 s]
[INFO] Process Control System Operator Interface Webapp ... SUCCESS [ 
20.761 s]
[INFO] OODT Process Control System JAX-RS service layer ... SUCCESS [  
8.773 s]
[INFO] Apache OODT  SUCCESS [ 
13.709 s]
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 09:23 min
[INFO] Finished at: 2018-02-26T20:31:43-08:00
[INFO] Final Memory: 137M/1559M
[INFO] 

nonas:oodt mattmann$ 
```


> Netty Transceiver throws an NPE
> ---
>
> Key: OODT-970
> URL: https://issues.apache.org/jira/browse/OODT-970
> Project: OODT
>  Issue Type: Test
>  Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
>Priority: Major
> Fix For: 1.9
>
>
> Netty transceiver throws an NPE whenever the Avro File Manager client is 
> called after the first time. 
> {code:java}
> java.lang.NullPointerException: null
> ! at 
> org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:431)
> ! at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
> ! at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> ! at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:181)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
> ! at 
> org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:84)
> {code}
> Cause is: transceiver being closed after every use inside finally{} block.



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

[jira] [Commented] (OODT-970) Netty Transceiver throws an NPE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-970:
-

Github user IMS94 commented on the issue:

https://github.com/apache/oodt/pull/55
  
That's fine. Only required addition to this PR is to use JUnit annotations  
instead of extending **TestCase**. may be I can do it later.


> Netty Transceiver throws an NPE
> ---
>
> Key: OODT-970
> URL: https://issues.apache.org/jira/browse/OODT-970
> Project: OODT
>  Issue Type: Test
>  Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
>Priority: Major
> Fix For: 1.9
>
>
> Netty transceiver throws an NPE whenever the Avro File Manager client is 
> called after the first time. 
> {code:java}
> java.lang.NullPointerException: null
> ! at 
> org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:431)
> ! at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
> ! at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> ! at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:181)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
> ! at 
> org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:84)
> {code}
> Cause is: transceiver being closed after every use inside finally{} block.



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

[jira] [Commented] (OODT-970) Netty Transceiver throws an NPE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-970:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/55
  
i'm going to go ahead and commit this. It's sat too long and it's useful in 
its current form.


> Netty Transceiver throws an NPE
> ---
>
> Key: OODT-970
> URL: https://issues.apache.org/jira/browse/OODT-970
> Project: OODT
>  Issue Type: Test
>  Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
>Priority: Major
> Fix For: 1.9
>
>
> Netty transceiver throws an NPE whenever the Avro File Manager client is 
> called after the first time. 
> {code:java}
> java.lang.NullPointerException: null
> ! at 
> org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:431)
> ! at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
> ! at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> ! at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:181)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
> ! at 
> org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:84)
> {code}
> Cause is: transceiver being closed after every use inside finally{} block.



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

[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

[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

[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

[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] [Commented] (OODT-970) Netty Transceiver throws an NPE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-970:
-

Github user IMS94 commented on a diff in the pull request:

https://github.com/apache/oodt/pull/55#discussion_r160733767
  
--- Diff: 
filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/AbstractFileManagerServerTest.java
 ---
@@ -0,0 +1,172 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.oodt.cas.filemgr.system;
+
+import junit.framework.TestCase;
+import org.apache.oodt.cas.filemgr.ingest.StdIngester;
+import org.apache.oodt.cas.filemgr.metadata.CoreMetKeys;
+import org.apache.oodt.cas.metadata.Metadata;
+import org.apache.oodt.cas.metadata.SerializableMetadata;
+
+import java.io.File;
+import java.io.FileInputStream;
+import java.net.URL;
+import java.util.Properties;
+import java.util.logging.Logger;
+
+public abstract class AbstractFileManagerServerTest extends TestCase {
+
+private static final Logger LOG = 
Logger.getLogger(AbstractFileManagerServerTest.class.getName());
--- End diff --

Sure. Thank you again. I will fix the others. I will try to make the 
logging consistent in the future since I believe that logging helps a lot when 
debugging. ;-)


> Netty Transceiver throws an NPE
> ---
>
> Key: OODT-970
> URL: https://issues.apache.org/jira/browse/OODT-970
> Project: OODT
>  Issue Type: Test
>  Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
> Fix For: 1.9
>
>
> Netty transceiver throws an NPE whenever the Avro File Manager client is 
> called after the first time. 
> {code:java}
> java.lang.NullPointerException: null
> ! at 
> org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:431)
> ! at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
> ! at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> ! at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:181)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
> ! at 
> org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:84)
> {code}
> Cause is: transceiver being closed after every use inside finally{} block.



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

[jira] [Commented] (OODT-970) Netty Transceiver throws an NPE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-970:
-

Github user lewismc commented on a diff in the pull request:

https://github.com/apache/oodt/pull/55#discussion_r160731753
  
--- Diff: 
filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/AbstractFileManagerServerTest.java
 ---
@@ -0,0 +1,172 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.oodt.cas.filemgr.system;
+
+import junit.framework.TestCase;
+import org.apache.oodt.cas.filemgr.ingest.StdIngester;
+import org.apache.oodt.cas.filemgr.metadata.CoreMetKeys;
+import org.apache.oodt.cas.metadata.Metadata;
+import org.apache.oodt.cas.metadata.SerializableMetadata;
+
+import java.io.File;
+import java.io.FileInputStream;
+import java.net.URL;
+import java.util.Properties;
+import java.util.logging.Logger;
+
+public abstract class AbstractFileManagerServerTest extends TestCase {
+
+private static final Logger LOG = 
Logger.getLogger(AbstractFileManagerServerTest.class.getName());
--- End diff --

Yes it is confusing. OK, please ignore my comment here then and consider 
the remaining comments, thank you.


> Netty Transceiver throws an NPE
> ---
>
> Key: OODT-970
> URL: https://issues.apache.org/jira/browse/OODT-970
> Project: OODT
>  Issue Type: Test
>  Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
> Fix For: 1.9
>
>
> Netty transceiver throws an NPE whenever the Avro File Manager client is 
> called after the first time. 
> {code:java}
> java.lang.NullPointerException: null
> ! at 
> org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:431)
> ! at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
> ! at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> ! at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:181)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
> ! at 
> org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:84)
> {code}
> Cause is: transceiver being closed after every use inside finally{} block.



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

[jira] [Commented] (OODT-970) Netty Transceiver throws an NPE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-970:
-

Github user IMS94 commented on a diff in the pull request:

https://github.com/apache/oodt/pull/55#discussion_r160729693
  
--- Diff: 
filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/AbstractFileManagerServerTest.java
 ---
@@ -0,0 +1,172 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.oodt.cas.filemgr.system;
+
+import junit.framework.TestCase;
+import org.apache.oodt.cas.filemgr.ingest.StdIngester;
+import org.apache.oodt.cas.filemgr.metadata.CoreMetKeys;
+import org.apache.oodt.cas.metadata.Metadata;
+import org.apache.oodt.cas.metadata.SerializableMetadata;
+
+import java.io.File;
+import java.io.FileInputStream;
+import java.net.URL;
+import java.util.Properties;
+import java.util.logging.Logger;
+
+public abstract class AbstractFileManagerServerTest extends TestCase {
+
+private static final Logger LOG = 
Logger.getLogger(AbstractFileManagerServerTest.class.getName());
--- End diff --

Thanks for the comments @lewismc! Well, the usage of logging is confusing 
since at some places it has used `java.util.Logging` and in some places it has 
used `slf4j API` with `log4j-slf4j implementation`. I personally prefer 
`slf4j`. But in these classes I kept what was being used.


> Netty Transceiver throws an NPE
> ---
>
> Key: OODT-970
> URL: https://issues.apache.org/jira/browse/OODT-970
> Project: OODT
>  Issue Type: Test
>  Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
> Fix For: 1.9
>
>
> Netty transceiver throws an NPE whenever the Avro File Manager client is 
> called after the first time. 
> {code:java}
> java.lang.NullPointerException: null
> ! at 
> org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:431)
> ! at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
> ! at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> ! at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:181)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
> ! at 
> org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:84)
> {code}
> Cause is: transceiver being closed after every use inside finally{} block.



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

[jira] [Commented] (OODT-970) Netty Transceiver throws an NPE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-970:
-

Github user lewismc commented on a diff in the pull request:

https://github.com/apache/oodt/pull/55#discussion_r160725828
  
--- Diff: 
filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/AbstractFileManagerServerTest.java
 ---
@@ -0,0 +1,172 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.oodt.cas.filemgr.system;
+
+import junit.framework.TestCase;
--- End diff --

Please change this to org.junit imports and associated anntoations


> Netty Transceiver throws an NPE
> ---
>
> Key: OODT-970
> URL: https://issues.apache.org/jira/browse/OODT-970
> Project: OODT
>  Issue Type: Test
>  Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
> Fix For: 1.9
>
>
> Netty transceiver throws an NPE whenever the Avro File Manager client is 
> called after the first time. 
> {code:java}
> java.lang.NullPointerException: null
> ! at 
> org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:431)
> ! at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
> ! at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> ! at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:181)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
> ! at 
> org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:84)
> {code}
> Cause is: transceiver being closed after every use inside finally{} block.



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

[jira] [Commented] (OODT-970) Netty Transceiver throws an NPE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-970:
-

Github user lewismc commented on a diff in the pull request:

https://github.com/apache/oodt/pull/55#discussion_r160726078
  
--- Diff: 
filemgr/src/test/java/org/apache/oodt/cas/filemgr/system/AbstractFileManagerServerTest.java
 ---
@@ -0,0 +1,172 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.oodt.cas.filemgr.system;
+
+import junit.framework.TestCase;
+import org.apache.oodt.cas.filemgr.ingest.StdIngester;
+import org.apache.oodt.cas.filemgr.metadata.CoreMetKeys;
+import org.apache.oodt.cas.metadata.Metadata;
+import org.apache.oodt.cas.metadata.SerializableMetadata;
+
+import java.io.File;
+import java.io.FileInputStream;
+import java.net.URL;
+import java.util.Properties;
+import java.util.logging.Logger;
+
+public abstract class AbstractFileManagerServerTest extends TestCase {
+
+private static final Logger LOG = 
Logger.getLogger(AbstractFileManagerServerTest.class.getName());
--- End diff --

I think we use Slf4j over Log4j... maybe I am wrong.


> Netty Transceiver throws an NPE
> ---
>
> Key: OODT-970
> URL: https://issues.apache.org/jira/browse/OODT-970
> Project: OODT
>  Issue Type: Test
>  Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
> Fix For: 1.9
>
>
> Netty transceiver throws an NPE whenever the Avro File Manager client is 
> called after the first time. 
> {code:java}
> java.lang.NullPointerException: null
> ! at 
> org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:431)
> ! at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
> ! at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> ! at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:181)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
> ! at 
> org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:84)
> {code}
> Cause is: transceiver being closed after every use inside finally{} block.



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

[jira] [Commented] (OODT-970) Netty Transceiver throws an NPE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-970:
-

Github user lewismc commented on a diff in the pull request:

https://github.com/apache/oodt/pull/55#discussion_r160724998
  
--- Diff: core/pom.xml ---
@@ -74,6 +74,16 @@ the License.
 aws-java-sdk
 1.7.4
   
+  
+org.apache.avro
+avro-ipc
--- End diff --

Can you please make the ```avro.version``` a defined property within the 
`` element. Then it can be used consistently.


> Netty Transceiver throws an NPE
> ---
>
> Key: OODT-970
> URL: https://issues.apache.org/jira/browse/OODT-970
> Project: OODT
>  Issue Type: Test
>  Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
> Fix For: 1.9
>
>
> Netty transceiver throws an NPE whenever the Avro File Manager client is 
> called after the first time. 
> {code:java}
> java.lang.NullPointerException: null
> ! at 
> org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:431)
> ! at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
> ! at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> ! at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:181)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
> ! at 
> org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:84)
> {code}
> Cause is: transceiver being closed after every use inside finally{} block.



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

[jira] [Commented] (OODT-970) Netty Transceiver throws an NPE

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-970:
-

GitHub user IMS94 opened a pull request:

https://github.com/apache/oodt/pull/55

Fix for [OODT-970] and [OODT-969] - Tests for Avro File Manager

Tests for Avro File Manager and solve the NPE problem in NettyTransceiver 
when Avro File Manager being called

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/IMS94/oodt development

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/55.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #55


commit 36f320e35155ff38eebdde60fb90a07074ad4148
Author: Imesha Sudasingha 
Date:   2018-01-10T10:59:41Z

This fixes [OODT-970] and [OODT-969] - Tests for Avro File Manager and 
solve the NPE problem in NettyTransceiver.




> Netty Transceiver throws an NPE
> ---
>
> Key: OODT-970
> URL: https://issues.apache.org/jira/browse/OODT-970
> Project: OODT
>  Issue Type: Test
>  Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
> Fix For: 1.9
>
>
> Netty transceiver throws an NPE whenever the Avro File Manager client is 
> called after the first time. 
> {code:java}
> java.lang.NullPointerException: null
> ! at 
> org.apache.avro.ipc.NettyTransceiver.getRemoteName(NettyTransceiver.java:431)
> ! at org.apache.avro.ipc.Requestor.writeHandshake(Requestor.java:202)
> ! at org.apache.avro.ipc.Requestor.access$300(Requestor.java:52)
> ! at org.apache.avro.ipc.Requestor$Request.getBytes(Requestor.java:478)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:181)
> ! at org.apache.avro.ipc.Requestor.request(Requestor.java:129)
> ! at 
> org.apache.avro.ipc.specific.SpecificRequestor.invoke(SpecificRequestor.java:84)
> {code}
> Cause is: transceiver being closed after every use inside finally{} block.



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

[jira] [Commented] (OODT-966) agility broken syntax under Python 3.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-966:
-

GitHub user lewismc opened a pull request:

https://github.com/apache/oodt/pull/54

OODT-966 agility broken syntax under Python 3.X

Hi @nutjob4life tagging you here FYI. This issue is primarily meant to 
address https://issues.apache.org/jira/browse/OODT-966 but as you can see it 
quickly got out of control when attempting to upgrade agility to be used with 
Python 3.X
Several failing tests, i will have a look when I get more time.
Lewis

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lewismc/oodt OODT-966

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/54.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #54


commit 5aa8bf47146f046e7540dc22ec22b5411241eb68
Author: Lewis John McGibbney 
Date:   2017-11-09T23:14:26Z

OODT-966 agility broken syntax under Python 3.X




> agility broken syntax under Python 3.X
> --
>
> Key: OODT-966
> URL: https://issues.apache.org/jira/browse/OODT-966
> Project: OODT
>  Issue Type: Bug
>  Components: agility
>Affects Versions: 1.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
>
> Using OODT master branch, python setup.py install results in the following
> {code}
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py to 
> webgrid.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/webgrid.py", line 51
> except Exception, e:
> ^
> SyntaxError: invalid syntax
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py to 
> workflow.cpython-36.pyc
>   File "build/bdist.macosx-10.7-x86_64/egg/oodt/workflow.py", line 129
> print 'available events:', events
> ^
> SyntaxError: Missing parentheses in call to 'print'
> byte-compiling build/bdist.macosx-10.7-x86_64/egg/oodt/xmlutils.py to 
> xmlutils.cpython-36.pyc
> creating build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/PKG-INFO -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/SOURCES.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/dependency_links.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/entry_points.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/namespace_packages.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/top_level.txt -> 
> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> copying oodt.egg-info/zip-safe -> build/bdist.macosx-10.7-x86_64/egg/EGG-INFO
> creating dist
> creating 'dist/oodt-1.2.dev_r0-py3.6.egg' and adding 
> 'build/bdist.macosx-10.7-x86_64/egg' to it
> removing 'build/bdist.macosx-10.7-x86_64/egg' (and everything under it)
> Processing oodt-1.2.dev_r0-py3.6.egg
> Copying oodt-1.2.dev_r0-py3.6.egg to 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages
> Adding oodt 1.2.dev-r0 to easy-install.pth file
> Installing webgrid script to /Users/lmcgibbn/miniconda3/bin
> Installed 
> /Users/lmcgibbn/miniconda3/lib/python3.6/site-packages/oodt-1.2.dev_r0-py3.6.egg
> Processing dependencies for oodt===1.2.dev-r0
> Finished processing dependencies for oodt===1.2.dev-r0
> {code}
> Fix coming up



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

[jira] [Commented] (OODT-933) @Deprecate all XMLRPC Code

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-933:
-

Github user asfgit closed the pull request at:

https://github.com/apache/oodt/pull/41


> @Deprecate all XMLRPC Code
> --
>
> Key: OODT-933
> URL: https://issues.apache.org/jira/browse/OODT-933
> Project: OODT
>  Issue Type: Task
>  Components: avro rpc
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 1.9
>
>
> In an attempt to move towards use of the preferred AvroRPC work undertaken by 
> [~radu.manole], this issue should @ Deprecate all of the existing XMLRPC code 
> with pointers to the new implementations. 



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

[jira] [Commented] (OODT-963) Workflow Manager Tests fail due to ZK-config feature

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-963:
-

Github user asfgit closed the pull request at:

https://github.com/apache/oodt/pull/53


> Workflow Manager Tests fail due to ZK-config feature
> 
>
> Key: OODT-963
> URL: https://issues.apache.org/jira/browse/OODT-963
> Project: OODT
>  Issue Type: Bug
>  Components: workflow manager
>Affects Versions: 1.2
>Reporter: Imesha Sudasingha
>Assignee: Chris A. Mattmann
>
> Following errors occur when running the tests related to the workflow manager:
> [https://paste.apache.org/Vd4a]
> it seems that the ZK config publishes workflow configuration here:
> */projects/primary/components/wmgr/*. 
> But then expects to read it here:
> */oodt/projects/default/components/wmgr*



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

[jira] [Commented] (OODT-963) Workflow Manager Tests fail due to ZK-config feature

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-963:
-

GitHub user IMS94 opened a pull request:

https://github.com/apache/oodt/pull/53

[OODT-963] [OODT-964] [OODT-965] Added configuration listening feature and 
fixed workflow manager tests

Contains fix for workflow manager test failures and improvement for 
distributed configuration management to listen for configuration changes

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/IMS94/oodt development

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/53.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #53


commit df1db1e44b3289214693f3a0894681400782ba99
Author: Imesha Sudasingha 
Date:   2017-08-19T10:51:10Z

[OODT-965] Added configuration change listening feature

commit 07aea0d364d6911a8a70221f3f6087749dc4e379
Author: Imesha Sudasingha 
Date:   2017-08-23T14:02:48Z

Improved java docs

commit 54089cae98a30b7953d848117bd3d1994185f5b1
Author: Imesha Sudasingha 
Date:   2017-10-11T10:00:34Z

Merge branch 'feature/zookeeper-config' of https://github.com/IMS94/oodt 
into development

commit c7d0842d9490fcf95f3ba0e07c1dc3cd8b16b76a
Author: Imesha Sudasingha 
Date:   2017-10-11T12:49:28Z

[OODT-963] Fixed surefire test failures in workflow manager due to forkMode

commit b52f235f799502ed04dc11da200f9cbe2650fced
Author: Imesha Sudasingha 
Date:   2017-10-11T17:24:03Z

[OODT-964] Removed empty test/workflow.properties which caused wmgr tests 
fail




> Workflow Manager Tests fail due to ZK-config feature
> 
>
> Key: OODT-963
> URL: https://issues.apache.org/jira/browse/OODT-963
> Project: OODT
>  Issue Type: Bug
>  Components: workflow manager
>Affects Versions: 1.2
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
>
> Following errors occur when running the tests related to the workflow manager:
> [https://paste.apache.org/Vd4a]
> it seems that the ZK config publishes workflow configuration here:
> */projects/primary/components/wmgr/*. 
> But then expects to read it here:
> */oodt/projects/default/components/wmgr*



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

[jira] [Commented] (OODT-963) Workflow Manager Tests fail due to ZK-config feature

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-963:
-

Github user IMS94 closed the pull request at:

https://github.com/apache/oodt/pull/52


> Workflow Manager Tests fail due to ZK-config feature
> 
>
> Key: OODT-963
> URL: https://issues.apache.org/jira/browse/OODT-963
> Project: OODT
>  Issue Type: Bug
>  Components: workflow manager
>Affects Versions: 1.2
>Reporter: Imesha Sudasingha
>Assignee: Imesha Sudasingha
>
> Following errors occur when running the tests related to the workflow manager:
> [https://paste.apache.org/Vd4a]
> it seems that the ZK config publishes workflow configuration here:
> */projects/primary/components/wmgr/*. 
> But then expects to read it here:
> */oodt/projects/default/components/wmgr*



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 closed the pull request at:

https://github.com/apache/oodt/pull/51


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Imesha Sudasingha
>  Labels: gsoc2017, mentor
> Fix For: 1.3
>
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on the issue:

https://github.com/apache/oodt/pull/51
  
Included in #52 


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Imesha Sudasingha
>  Labels: gsoc2017, mentor
> Fix For: 1.3
>
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

GitHub user IMS94 opened a pull request:

https://github.com/apache/oodt/pull/52

 Fixed surefire test failures in workflow manager due to 

Workflow manager tests failed in when running `mvn clean install`. The 
problem was with the sure fire plugin in workflow manager. `` was set 
to `never` earlier. This has caused some environment variables I was setting 
through surefire to affect other tests as well. Changed it to `pertest`. Tests 
are passing now, except 
`org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager` due to a NPE 
which requires to be addressed separately.

This PR also include some missing commits which adds the feature to watch 
for configuration changes and act accordingly for **[OODT-945]**

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/IMS94/oodt development

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/52.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #52


commit 711b445cf3d5964ebff8fd72e06fbfc451a19ff0
Author: Imesha Sudasingha 
Date:   2017-08-19T10:51:10Z

Added configuration change listening feature

commit bd86cd657516eb221759920e941b84322a8a52e6
Author: Imesha Sudasingha 
Date:   2017-08-23T14:02:48Z

Improved java docs

commit fb6c2fad13c6ff7f107b6f6147e661996ed74a27
Author: Imesha Sudasingha 
Date:   2017-10-11T10:00:34Z

Merge branch 'feature/zookeeper-config' of https://github.com/IMS94/oodt 
into development

commit f8a9b284a7fed1b5e1b120cfdb2a52fedb539c26
Author: Imesha Sudasingha 
Date:   2017-10-11T12:49:28Z

Fixed surefire test failures in workflow manager due to 




> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Imesha Sudasingha
>  Labels: gsoc2017, mentor
> Fix For: 1.3
>
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/50
  
reviewed, and tested! LGTM and committed!


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
> Fix For: 1.3
>
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

GitHub user IMS94 opened a pull request:

https://github.com/apache/oodt/pull/50

[OODT-945] Introduced distributed configuration management for workflow and 
resource managers

Up to now, distributed configuration management was tested and implemented 
for file manager only (#44 and #48). This PR is introducing the same for both 
workflow manager and resource manager. 

This also include corresponding unit tests to ensure functionality of those 
components with distributed configuration management enabled.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/IMS94/oodt feature/zookeeper-config

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/50.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #50


commit 57a9235e71a9d869291e80ba9bd16eeddd4a8e10
Author: Imesha Sudasingha 
Date:   2017-08-06T09:34:36Z

Merge branch 'master' of https://github.com/apache/oodt into 
feature/zookeeper-config

commit 9ee8af48ba45904a44d4e32b3030e8ad7d0bee21
Author: Imesha Sudasingha 
Date:   2017-08-10T13:02:27Z

Improvements to filemgr and config-publisher bash scripts

commit c437106fb9292547f8d87ada4601aab6b9d97ee9
Author: Imesha Sudasingha 
Date:   2017-08-10T13:03:18Z

Merge branch 'feature/zookeeper-config' of https://github.com/apache/oodt 
into feature/zookeeper-config

commit 57e544658f0716395c78b3c0cdaa3875b1c2cdff
Author: Imesha Sudasingha 
Date:   2017-08-12T06:51:29Z

Added cleaning up directories created when testing file manager

commit ef0aa5a75ff5fad964b7a0c5dfb7f6d5ea500484
Author: Tom Barber 
Date:   2017-08-14T22:07:38Z

update changes for 1.2

commit 7443a7c37a993afffa66270282a6a6c5aa8074ba
Author: Tom Barber 
Date:   2017-08-14T22:31:51Z

update version

commit 3df0e43de5f8c78348cff5da766e75f62343a380
Author: Imesha Sudasingha 
Date:   2017-08-15T17:01:30Z

Merge branch 'master' of https://github.com/apache/oodt into 
feature/zookeeper-config

commit fc6311db2ed4e5ccc6129cb88c71bb5428037b98
Author: Imesha Sudasingha 
Date:   2017-08-15T19:47:42Z

Introduced distributed configuration management to workflow and resource 
managers + tests




> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
> Fix For: 1.3
>
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/48
  
build passes, all tests pass, and code looks  

committing!

```
[INFO] >>> maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) > 
generate-sources @ oodt >>>
[INFO] 
[INFO] <<< maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) < 
generate-sources @ oodt <<<
[INFO] 
[INFO] --- maven-javadoc-plugin:2.10.3:javadoc (attach-javadocs) @ oodt ---
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ oodt ---
[INFO] Installing /Users/mattmann/git/oodt/pom.xml to 
/Users/mattmann/.m2/repository/org/apache/oodt/oodt/1.2-SNAPSHOT/oodt-1.2-SNAPSHOT.pom
[INFO] 

[INFO] Reactor Summary:
[INFO] 
[INFO] OODT Core .. SUCCESS [  
1.465 s]
[INFO] Common Utilities ... SUCCESS [ 
17.148 s]
[INFO] CAS Command Line Interface . SUCCESS [  
4.770 s]
[INFO] OODT - Configuration Management  SUCCESS [  
5.153 s]
[INFO] Process Control System Input Data Package .. SUCCESS [  
1.305 s]
[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container 
SUCCESS [  2.218 s]
[INFO] Catalog and Archive File Management Component .. SUCCESS [02:20 
min]
[INFO] Catalog and Archive Resource Management Component .. SUCCESS [ 
15.761 s]
[INFO] Catalog and Archive Workflow Management Component .. SUCCESS [ 
25.660 s]
[INFO] Catalog and Archive Crawling Framework . SUCCESS [ 
14.219 s]
[INFO] OODT CAS Curator Single Sign On Security Package ... SUCCESS [  
1.307 s]
[INFO] CAS Curation Web Services .. SUCCESS [  
6.256 s]
[INFO] Process Control System Core Package  SUCCESS [ 
11.753 s]
[INFO] OODT Wicket Web Components . SUCCESS [  
3.793 s]
[INFO] CAS Curation Interface . SUCCESS [  
7.610 s]
[INFO] CAS PGE Adaptor Framework .. SUCCESS [ 
13.339 s]
[INFO] CAS Installer Maven Mojo ... SUCCESS [  
2.329 s]
[INFO] OODT :: Archetypes :: OpsUI  SUCCESS [  
0.821 s]
[INFO] OODT :: Archetypes :: RADiX  SUCCESS [  
0.978 s]
[INFO] OODT :: Archetypes . SUCCESS [  
0.024 s]
[INFO] CAS File Manager Browser Web App ... SUCCESS [  
7.333 s]
[INFO] CAS Workflow Manager Monitor Web App ... SUCCESS [  
3.690 s]
[INFO] CAS Product Server Web Application . SUCCESS [  
9.914 s]
[INFO] CAS Workflow REST Services . SUCCESS [  
2.872 s]
[INFO] Process Control System Operator Interface Webapp ... SUCCESS [ 
11.993 s]
[INFO] OODT Process Control System JAX-RS service layer ... SUCCESS [  
4.930 s]
[INFO] Apache OODT  SUCCESS [  
0.019 s]
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 05:17 min
[INFO] Finished at: 2017-08-09T10:07:27-07:00
[INFO] Final Memory: 107M/1465M
[INFO] 

LMC-053601:oodt mattmann$ 
```
thanks @IMS94 


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user asfgit closed the pull request at:

https://github.com/apache/oodt/pull/48


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/48
  
will review tomorrow


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on the issue:

https://github.com/apache/oodt/pull/48
  
hey @chrismattmann, Should be ok now?


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/48
  
hey @IMS94 can you squash/rebase your local and then resubmit your PR? I'm 
getting a bunch of changes that are already there in the remote branch. Try git 
pull before you rebase.


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on the issue:

https://github.com/apache/oodt/pull/44
  
@chrismattmann Thanks for your support too. Did the tests pass for you 
without a problem?


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/44
  
merged this thanks @IMS94 

```
LMC-053601:oodt mattmann$ git push -u origin feature/zookeeper-config
Counting objects: 475, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (203/203), done.
Writing objects: 100% (475/475), 81.85 KiB | 0 bytes/s, done.
Total 475 (delta 155), reused 355 (delta 113)
remote: oodt git commit: Update log4j config.
remote: oodt git commit: Merge branch 'feature/zookeeper-config' of 
https://github.com/IMS94/oodt into feature/zookeeper-config
remote: oodt git commit: assert not null.
remote: oodt git commit: Fix for empty component home variable
remote: oodt git commit: Merge and apply robust changes for stack trace 
print in tests.
remote: oodt git commit: Merge branch 'feature/zookeeper-config' of 
https://github.com/IMS94/oodt into feature/zookeeper-config
remote: oodt git commit: fix for presence of component home environment 
variables in tests
remote: oodt git commit: Merge branch 'feature/zookeeper-config' of 
https://github.com/IMS94/oodt into feature/zookeeper-config
remote: oodt git commit: fix pom.xml
remote: oodt git commit: Fixed parent artifactId in config/pom.xml
remote: oodt git commit: Removed * imports. Improved code formatting and 
refactored code.
remote: oodt git commit: Merge branch 'master' of 
https://github.com/apache/oodt into feature/zookeeper-config
remote: oodt git commit: Update README.md
remote: oodt git commit: Merge branch 'OODT-847' of 
http://github.com/adhulipa/oodt
remote: oodt git commit: Record change for OODT-847.
remote: oodt git commit: Merge branch 'master' into feature/zookeeper-config
remote: oodt git commit: Improvements to file downloading from zookeeper 
and tests
remote: oodt git commit: Minor improvements for configuration manager tests
remote: oodt git commit: Created test cases for distributed configuration 
manager and publisher
remote: oodt git commit: Added zip packaging for distributed configuration 
publisher
remote: oodt git commit: Implemented configuration fetching for 
DistributedConfigurationManager
remote: oodt git commit: Altered configuration publishing mechanism to use 
spring configuration
remote: oodt git commit: Implemented global configuration publishing 
mechanism.
remote: oodt git commit: Defined initial API for ConfigurationManager
remote: oodt git commit: Fix for OODT-847 contributed by adhulipa & rverma
To https://git-wip-us.apache.org/repos/asf/oodt.git
   ec5b201..3fb7660  feature/zookeeper-config -> feature/zookeeper-config
Branch feature/zookeeper-config set up to track remote branch 
feature/zookeeper-config from origin.
LMC-053601:oodt mattmann$ 
```


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on the issue:

https://github.com/apache/oodt/pull/44
  
Hi @chrismattmann, Thanks for the invitation. 

I have pushed an update. There's still a chance for the tests to fail 
because I store configuration files in `${COMPONENT_HOME}` directory if 
`${COMPONENT_HOME}` is present, else in the working directory. If it fails 
again, I will find a more convenient method for my implementation.


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/44
  
OK @IMS94 I have invited you to the USC Data Science slack 


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/44
  
@IMS94 feel free to request an invite to uscdatascience.slack.com I'll make 
a channel for slack chat if you want real time comm on this


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on the issue:

https://github.com/apache/oodt/pull/44
  
Hi @chrismattmann, Thanks for the update. That is the reason for the test 
failure. Actually this is a case I should have addressed within my code. I have 
wrote the fix. Will push it now. 


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on the issue:

https://github.com/apache/oodt/pull/44
  
Hi @chrismattmann, No. Tests do not require any environment variable to be 
set. But if any of the above mentioned env variables are set, that could be a 
possible reason for your test failure (because I didn't encounter test 
failures). I'm using environment variables to determine each OODT component's 
HOME when downloading and storing configuration files from zookeeper.

Therefore, what I wanted know was whether you have any of those env vars 
set.


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/44
  
So I checked, and I do have those environment variables set, except for 
```RESMGR_HOME``` e.g., 

```
LMC-053601:oodt mattmann$ echo $FILEMGR_HOME
/usr/local/bigtranslate/filemgr
LMC-053601:oodt mattmann$ echo $FILEMGR_URL
http://localhost:9000
LMC-053601:oodt mattmann$ 
LMC-053601:oodt mattmann$ echo $RESMGR_URL
http://localhost:9002
LMC-053601:oodt mattmann$ 
```

I was thinking about your code - is it that if an environment variable from 
local config isn't that set - you are publishing a null value to ZK or there is 
a getPropertyOrNull call somewhere that is causing this? If so, we should 
probably have a sensibleDefaults() configuration which are all the sensible 
defaults in case the environment is Null. Even better would be to use PathUtils 
in o.a.cas.metadata.util to do EnvVarOrMetadata replacement on all paths you 
read from config.




> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/44
  
hi @IMS94 do I need to set those env vars? This will screw up tests since 
they should not have environment variable requirements, or if so, should be 
mock'ed in the tests themselves.


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on the issue:

https://github.com/apache/oodt/pull/44
  
Hi @chrismattmann, Can let me know do you have any of previously set up 
`FILEMGR_HOME` or `RESMGR_HOME` environment variables available in your system? 


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/44
  
hi @IMS94 got further, but failing on unit tests, thoughts?

```
---
 T E S T S
---
Running 
org.apache.oodt.config.distributed.DistributedConfigurationManagerTest
log4j:WARN No appenders could be found for logger 
(org.apache.zookeeper.server.quorum.QuorumPeerConfig).
log4j:WARN Please initialize the log4j system properly.
Starting configuration publishing

Processing commands for component : FILE_MANAGER
Publishing configuration for : FILE_MANAGER
Published configuration for : FILE_MANAGER


Processing commands for component : RESOURCE_MANAGER
Publishing configuration for : RESOURCE_MANAGER
Published configuration for : RESOURCE_MANAGER

Starting configuration publishing

Processing commands for component : FILE_MANAGER
Clearing configuration for : FILE_MANAGER
Cleared configuration for : FILE_MANAGER


Processing commands for component : RESOURCE_MANAGER
Clearing configuration for : RESOURCE_MANAGER
Cleared configuration for : RESOURCE_MANAGER

Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.209 sec 
<<< FAILURE! - in 
org.apache.oodt.config.distributed.DistributedConfigurationManagerTest

loadConfigurationTest(org.apache.oodt.config.distributed.DistributedConfigurationManagerTest)
  Time elapsed: 0.049 sec  <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at 
org.apache.oodt.config.distributed.DistributedConfigurationManagerTest.loadConfigurationTest(DistributedConfigurationManagerTest.java:91)

Running 
org.apache.oodt.config.distributed.DistributedConfigurationPublisherTest
Starting configuration publishing

Processing commands for component : FILE_MANAGER
Publishing configuration for : FILE_MANAGER
Published configuration for : FILE_MANAGER

Verifying configuration for : FILE_MANAGER
OK... Configuration verified
Verified configuration for : FILE_MANAGER


Processing commands for component : RESOURCE_MANAGER
Publishing configuration for : RESOURCE_MANAGER
Published configuration for : RESOURCE_MANAGER

Verifying configuration for : RESOURCE_MANAGER
OK... Configuration verified
Verified configuration for : RESOURCE_MANAGER

Starting configuration publishing

Processing commands for component : FILE_MANAGER
Clearing configuration for : FILE_MANAGER
Cleared configuration for : FILE_MANAGER


Processing commands for component : RESOURCE_MANAGER
Clearing configuration for : RESOURCE_MANAGER
Cleared configuration for : RESOURCE_MANAGER

Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.512 sec - 
in org.apache.oodt.config.distributed.DistributedConfigurationPublisherTest

Results :

Failed tests: 
  DistributedConfigurationManagerTest.loadConfigurationTest:91 null

Tests run: 2, Failures: 1, Errors: 0, Skipped: 0

[INFO] 

[INFO] Reactor Summary:
[INFO] 
[INFO] OODT Core .. SUCCESS [  
1.820 s]
[INFO] Common Utilities ... SUCCESS [ 
17.797 s]
[INFO] CAS Command Line Interface . SUCCESS [  
6.046 s]
[INFO] OODT - Configuration Management  FAILURE [  
5.426 s]
[INFO] Process Control System Input Data Package .. SKIPPED
[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container 
SKIPPED
[INFO] CAS Protocol ... SKIPPED
[INFO] CAS Protocol FTP Implementation  SKIPPED
[INFO] CAS Protocol HTTP Implementation ... SKIPPED
[INFO] CAS Protocol IMAPS Implementation .. SKIPPED
[INFO] CAS Protocol SFTP Implementation ... SKIPPED
[INFO] Query Expression ... SKIPPED
[INFO] OODT Single Sign On Security Package ... SKIPPED
[INFO] Catalog and Archive File Management Component .. SKIPPED
[INFO] OODT CAS Virtual Catalog and Integration Service. .. SKIPPED
[INFO] Catalog and Archive Resource Management Component .. SKIPPED
[INFO] Catalog and Archive Workflow Management Component 

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on the issue:

https://github.com/apache/oodt/pull/44
  
Hi @chrismattmann, can you check now? I had put wrong parent artifactId 
name in `config/pom.xml` earlier. It should build now.


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/44
  
hi @IMS94 I have errors building this locally can you check:

```
LMC-053601:oodt mattmann$ mvn clean install
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] 'parent.relativePath' of POM 
org.apache.oodt:oodt-conf:[unknown-version] 
(/Users/mattmann/git/oodt/config/pom.xml) points at org.apache.oodt:oodt-core 
instead of org.apache.oodt:oodt, please verify your project structure @ 
org.apache.oodt:oodt-conf:[unknown-version], 
/Users/mattmann/git/oodt/config/pom.xml, line 5, column 13
[ERROR] 'dependencies.dependency.version' for 
org.apache.curator:curator-framework:jar is missing. @ 
org.apache.oodt:oodt-conf:[unknown-version], 
/Users/mattmann/git/oodt/config/pom.xml, line 19, column 21
[ERROR] 'dependencies.dependency.version' for args4j:args4j:jar is missing. 
@ org.apache.oodt:oodt-conf:[unknown-version], 
/Users/mattmann/git/oodt/config/pom.xml, line 39, column 21
[ERROR] 'dependencies.dependency.version' for 
org.apache.curator:curator-test:jar is missing. @ 
org.apache.oodt:oodt-conf:[unknown-version], 
/Users/mattmann/git/oodt/config/pom.xml, line 55, column 21
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project org.apache.oodt:oodt-conf:1.1-SNAPSHOT 
(/Users/mattmann/git/oodt/config/pom.xml) has 3 errors
[ERROR] 'dependencies.dependency.version' for 
org.apache.curator:curator-framework:jar is missing. @ 
org.apache.oodt:oodt-conf:[unknown-version], 
/Users/mattmann/git/oodt/config/pom.xml, line 19, column 21
[ERROR] 'dependencies.dependency.version' for args4j:args4j:jar is 
missing. @ org.apache.oodt:oodt-conf:[unknown-version], 
/Users/mattmann/git/oodt/config/pom.xml, line 39, column 21
[ERROR] 'dependencies.dependency.version' for 
org.apache.curator:curator-test:jar is missing. @ 
org.apache.oodt:oodt-conf:[unknown-version], 
/Users/mattmann/git/oodt/config/pom.xml, line 55, column 21
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
```



> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on a diff in the pull request:

https://github.com/apache/oodt/pull/44#discussion_r126652721
  
--- Diff: README.md ---
@@ -53,8 +50,7 @@ To contribute a patch, follow these instructions (note 
that installing
 ```
 
 
-License (see also LICENSE.txt)
-==
+## License (see also LICENSE.txt)
--- End diff --

Hi @IMS94 I haven't applied *all of them*, just the *first one*, so can you 
please open a new PR with the other changes you did and remove/rollback this 
one.


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on a diff in the pull request:

https://github.com/apache/oodt/pull/44#discussion_r126597857
  
--- Diff: config/src/main/resources/examples/filemgr/cmd-line-actions.xml 
---
@@ -0,0 +1,123 @@
+
--- End diff --

thanks check out Maven Antrun plugin


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on a diff in the pull request:

https://github.com/apache/oodt/pull/44#discussion_r126577868
  
--- Diff: 
filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/XmlRpcFileManager.java 
---
@@ -52,29 +41,20 @@
 import org.apache.oodt.cas.metadata.Metadata;
 import org.apache.oodt.cas.metadata.exceptions.MetExtractionException;
 import org.apache.oodt.commons.date.DateUtils;
+import org.apache.oodt.config.ConfigurationManager;
+import org.apache.oodt.config.ConfigurationManagerFactory;
+import org.apache.oodt.config.Constants;
 import org.apache.xmlrpc.WebServer;
 
-import com.google.common.collect.Lists;
-
-import java.io.File;
-import java.io.FileInputStream;
-import java.io.FileNotFoundException;
-import java.io.FileOutputStream;
-import java.io.IOException;
+import java.io.*;
 import java.net.URI;
 import java.net.URISyntaxException;
 import java.net.URL;
-import java.util.Arrays;
-import java.util.Hashtable;
-import java.util.LinkedList;
-import java.util.List;
-import java.util.Map;
-import java.util.Vector;
+import java.util.*;
--- End diff --

@chrismattmann Sorry, it was my fault. I was using IntelliJ IDEA's optimize 
imports command. I will fix this.


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on a diff in the pull request:

https://github.com/apache/oodt/pull/44#discussion_r126577969
  
--- Diff: config/src/main/resources/examples/filemgr/cmd-line-actions.xml 
---
@@ -0,0 +1,123 @@
+
--- End diff --

@chrismattmann I will look into that. Thanks for pointing that out. Didn't 
know we can do that with a plugin before.


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on a diff in the pull request:

https://github.com/apache/oodt/pull/44#discussion_r126577697
  
--- Diff: README.md ---
@@ -53,8 +50,7 @@ To contribute a patch, follow these instructions (note 
that installing
 ```
 
 
-License (see also LICENSE.txt)
-==
+## License (see also LICENSE.txt)
--- End diff --

@chrismattmann Sure. But I think you have applied these changes to the 
Readme.md with the commit [update 
README.md](https://github.com/apache/oodt/commit/1b42cacacfc96e96b69f0c28d7eefcb89ae85856).
 Therefore, I will rollback this change


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on a diff in the pull request:

https://github.com/apache/oodt/pull/44#discussion_r126509803
  
--- Diff: config/src/main/resources/examples/filemgr/filemgr.properties ---
@@ -0,0 +1,114 @@
+#
--- End diff --

same why copy these when we can use some maven copy task


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-933) @Deprecate all XMLRPC Code

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-933:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/41
  
perfect let's do that @lewismc so we can get the AvroRPC stuff in there and 
just be done with it then stablize


> @Deprecate all XMLRPC Code
> --
>
> Key: OODT-933
> URL: https://issues.apache.org/jira/browse/OODT-933
> Project: OODT
>  Issue Type: Task
>  Components: avro rpc
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 1.1
>
>
> In an attempt to move towards use of the preferred AvroRPC work undertaken by 
> [~radu.manole], this issue should @ Deprecate all of the existing XMLRPC code 
> with pointers to the new implementations. 



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

[jira] [Commented] (OODT-933) @Deprecate all XMLRPC Code

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-933:
-

Github user buggtb commented on the issue:

https://github.com/apache/oodt/pull/41
  
@lewismc yeah shunt it over to development and it'll be good, thats where 
the ZK stuff will go shortly.


> @Deprecate all XMLRPC Code
> --
>
> Key: OODT-933
> URL: https://issues.apache.org/jira/browse/OODT-933
> Project: OODT
>  Issue Type: Task
>  Components: avro rpc
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 1.1
>
>
> In an attempt to move towards use of the preferred AvroRPC work undertaken by 
> [~radu.manole], this issue should @ Deprecate all of the existing XMLRPC code 
> with pointers to the new implementations. 



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/44
  
please see my review comments above - great start!


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/44
  
@IMS94 


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on a diff in the pull request:

https://github.com/apache/oodt/pull/44#discussion_r126509940
  
--- Diff: 
filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/XmlRpcFileManager.java 
---
@@ -52,29 +41,20 @@
 import org.apache.oodt.cas.metadata.Metadata;
 import org.apache.oodt.cas.metadata.exceptions.MetExtractionException;
 import org.apache.oodt.commons.date.DateUtils;
+import org.apache.oodt.config.ConfigurationManager;
+import org.apache.oodt.config.ConfigurationManagerFactory;
+import org.apache.oodt.config.Constants;
 import org.apache.xmlrpc.WebServer;
 
-import com.google.common.collect.Lists;
-
-import java.io.File;
-import java.io.FileInputStream;
-import java.io.FileNotFoundException;
-import java.io.FileOutputStream;
-import java.io.IOException;
+import java.io.*;
 import java.net.URI;
 import java.net.URISyntaxException;
 import java.net.URL;
-import java.util.Arrays;
-import java.util.Hashtable;
-import java.util.LinkedList;
-import java.util.List;
-import java.util.Map;
-import java.util.Vector;
+import java.util.*;
--- End diff --

we don't use star imports and these changes are orthogonal


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on a diff in the pull request:

https://github.com/apache/oodt/pull/44#discussion_r126509639
  
--- Diff: config/src/main/resources/examples/filemgr/cmd-line-actions.xml 
---
@@ -0,0 +1,123 @@
+
--- End diff --

maybe we should use maven-ant-tasks to copy these in the prepare-resources 
phase or in the compile phase (whatever you need them for) instead of 
physically copying the files?


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user chrismattmann commented on a diff in the pull request:

https://github.com/apache/oodt/pull/44#discussion_r126501802
  
--- Diff: README.md ---
@@ -53,8 +50,7 @@ To contribute a patch, follow these instructions (note 
that installing
 ```
 
 
-License (see also LICENSE.txt)
-==
+## License (see also LICENSE.txt)
--- End diff --

great changes, these are orthogonal though - can you separate them into a 
new PR apart from this?


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-847) New FilemgrMetExtractor to extract File System Attributes

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-847:
-

Github user asfgit closed the pull request at:

https://github.com/apache/oodt/pull/42


> New FilemgrMetExtractor to extract File System Attributes
> -
>
> Key: OODT-847
> URL: https://issues.apache.org/jira/browse/OODT-847
> Project: OODT
>  Issue Type: New Feature
>  Components: file manager
>Affects Versions: 0.8.1
>Reporter: Rishi Verma
>Assignee: Chris A. Mattmann
>Priority: Minor
> Fix For: 1.1
>
> Attachments: FileAttributesExtractor.java
>
>
> It's sometimes useful to extract File System metadata from files that people 
> often see when browsing a file on an operating system.
> Examples:
> * POSIX permissions
> * Datetime stamps, including: lastModified, creationTime, lastAccessTime
> * Is a symbolic file?
> * Is a directory?
> * File owner
> * Is hidden file?
> etc.
> Java 7's Files.getAttributes [1] does this in a platform-generic way. We 
> should leverage this and add an extractor for the benefit of the community.
> [1] http://docs.oracle.com/javase/tutorial/essential/io/fileAttr.html



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

[jira] [Commented] (OODT-933) @Deprecate all XMLRPC Code

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-933:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/41
  
team should we merge this? @lewismc @buggtb @Cyan3 


> @Deprecate all XMLRPC Code
> --
>
> Key: OODT-933
> URL: https://issues.apache.org/jira/browse/OODT-933
> Project: OODT
>  Issue Type: Task
>  Components: avro rpc
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 1.1
>
>
> In an attempt to move towards use of the preferred AvroRPC work undertaken by 
> [~radu.manole], this issue should @ Deprecate all of the existing XMLRPC code 
> with pointers to the new implementations. 



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

GitHub user IMS94 opened a pull request:

https://github.com/apache/oodt/pull/44

OODT-945 Rework OODT configuration to make use of Zookeeper for distributed 
configuration management (GSoC 2017)

This PR includes the Distributed Configuration Management implementation 
for OODT [OODT-945] along with the distributed configuration publishing CLI 
[OODT-952].

Explanation on the design of this feature is available at [Rework OODT 
configuration to make use of Zookeeper for distributed configuration 
management](https://cwiki.apache.org/confluence/display/OODT/Rework+OODT+configuration+to+make+use+of+Zookeeper+for+distributed+configuration+management).

User documentation on how to use this distributed configuration management 
feature is available at [OODT Distributed Configuration 
Management](https://cwiki.apache.org/confluence/display/OODT/OODT+Distributed+Configuration+Management)

Corresponding GSoC project proposal is available at 
[https://cwiki.apache.org/confluence/display/OODT/Proposal](https://cwiki.apache.org/confluence/display/OODT/Proposal)

**Since this is the first glance of the distributed configuration 
management feature, there can be bugs and improvements required to be 
addressed. Please review this PR and provide me with your kind feedback so that 
I can improve on that.**

Thank you!

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/IMS94/oodt feature/zookeeper-config

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/44.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #44


commit ac7170bdf5c973374f141c6f3e031fa748e0af13
Author: Imesha Sudasingha 
Date:   2017-04-01T07:00:55Z

Defined initial API for ConfigurationManager

commit 4b88f71497263675bb313462075fd552696ba717
Author: Imesha Sudasingha 
Date:   2017-06-16T10:23:43Z

Implemented global configuration publishing mechanism.

commit fadf149cb77dd943af9e81c0f127ce74f203c478
Author: Imesha Sudasingha 
Date:   2017-06-17T15:39:58Z

Altered configuration publishing mechanism to use spring configuration

commit 5fcf2220125b64afba080c6c9c6c5592daae2dea
Author: Imesha Sudasingha 
Date:   2017-06-17T17:51:12Z

Implemented configuration fetching for DistributedConfigurationManager

commit 27a28daa3d3c448b462bd9a33eb6ac4fd859b75a
Author: Imesha Sudasingha 
Date:   2017-07-02T15:23:49Z

Added zip packaging for distributed configuration publisher

commit a973c531fee5bf37ebf4448334470c75943af1ec
Author: Imesha Sudasingha 
Date:   2017-07-03T10:25:22Z

Created test cases for distributed configuration manager and publisher

commit e697405223fe17c96739ae8f156639a0f5ef321c
Author: Imesha Sudasingha 
Date:   2017-07-09T16:48:40Z

Minor improvements for configuration manager tests

commit 99b086b9887cafc8b89de3ff65fa61d3f80cc56c
Author: Imesha Sudasingha 
Date:   2017-07-10T11:51:51Z

Improvements to file downloading from zookeeper and tests

commit a8092af5484d066a4dda623395bf21612d696d62
Author: Imesha Sudasingha 
Date:   2017-07-10T14:24:28Z

Merge branch 'master' into feature/zookeeper-config




> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 commented on the issue:

https://github.com/apache/oodt/pull/43
  
Will open this again on a feature branch.


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

GitHub user IMS94 reopened a pull request:

https://github.com/apache/oodt/pull/43

OODT-945 Rework OODT configuration to make use of Zookeeper for distributed 
configuration management (GSoC 2017)

This PR includes the Distributed Configuration Management implementation 
for OODT [OODT-945] along with the distributed configuration publishing CLI 
[OODT-952].

Explanation on the design of this feature is available at [Rework OODT 
configuration to make use of Zookeeper for distributed configuration 
management](https://cwiki.apache.org/confluence/display/OODT/Rework+OODT+configuration+to+make+use+of+Zookeeper+for+distributed+configuration+management).

User documentation on how to use this distributed configuration management 
feature is available at [OODT Distributed Configuration 
Management](https://cwiki.apache.org/confluence/display/OODT/OODT+Distributed+Configuration+Management)

Corresponding GSoC project proposal is available at 
[https://cwiki.apache.org/confluence/display/OODT/Proposal](https://cwiki.apache.org/confluence/display/OODT/Proposal)

**Since this is the first glance of the distributed configuration 
management feature, there can be bugs and improvements required to be 
addressed. Please review this PR and provide me with your kind feedback so that 
I can improve on that**

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/IMS94/oodt master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/43.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #43






> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

Github user IMS94 closed the pull request at:

https://github.com/apache/oodt/pull/43


> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-945:
-

GitHub user IMS94 opened a pull request:

https://github.com/apache/oodt/pull/43

OODT-945 Rework OODT configuration to make use of Zookeeper for distributed 
configuration management (GSoC 2017)

This PR includes the Distributed Configuration Management implementation 
for OODT [OODT-945] along with the distributed configuration publishing CLI 
[OODT-952].

Explanation on the design of this feature is available at [Rework OODT 
configuration to make use of Zookeeper for distributed configuration 
management](https://cwiki.apache.org/confluence/display/OODT/Rework+OODT+configuration+to+make+use+of+Zookeeper+for+distributed+configuration+management).

User documentation on how to use this distributed configuration management 
feature is available at [OODT Distributed Configuration 
Management](https://cwiki.apache.org/confluence/display/OODT/OODT+Distributed+Configuration+Management)

Corresponding GSoC project proposal is available at 
[https://cwiki.apache.org/confluence/display/OODT/Proposal](https://cwiki.apache.org/confluence/display/OODT/Proposal)

**Since this is the first glance of the distributed configuration 
management feature, there can be bugs and improvements required to be 
addressed. Please review this PR and provide me with your kind feedback so that 
I can improve on that**

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/IMS94/oodt master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/43.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #43


commit ac7170bdf5c973374f141c6f3e031fa748e0af13
Author: Imesha Sudasingha 
Date:   2017-04-01T07:00:55Z

Defined initial API for ConfigurationManager

commit 4b88f71497263675bb313462075fd552696ba717
Author: Imesha Sudasingha 
Date:   2017-06-16T10:23:43Z

Implemented global configuration publishing mechanism.

commit fadf149cb77dd943af9e81c0f127ce74f203c478
Author: Imesha Sudasingha 
Date:   2017-06-17T15:39:58Z

Altered configuration publishing mechanism to use spring configuration

commit 5fcf2220125b64afba080c6c9c6c5592daae2dea
Author: Imesha Sudasingha 
Date:   2017-06-17T17:51:12Z

Implemented configuration fetching for DistributedConfigurationManager

commit 27a28daa3d3c448b462bd9a33eb6ac4fd859b75a
Author: Imesha Sudasingha 
Date:   2017-07-02T15:23:49Z

Added zip packaging for distributed configuration publisher

commit a973c531fee5bf37ebf4448334470c75943af1ec
Author: Imesha Sudasingha 
Date:   2017-07-03T10:25:22Z

Created test cases for distributed configuration manager and publisher

commit e697405223fe17c96739ae8f156639a0f5ef321c
Author: Imesha Sudasingha 
Date:   2017-07-09T16:48:40Z

Minor improvements for configuration manager tests

commit 99b086b9887cafc8b89de3ff65fa61d3f80cc56c
Author: Imesha Sudasingha 
Date:   2017-07-10T11:51:51Z

Improvements to file downloading from zookeeper and tests




> Rework OODT configuration to make use of  Zookeeper for distributed 
> configuration management
> 
>
> Key: OODT-945
> URL: https://issues.apache.org/jira/browse/OODT-945
> Project: OODT
>  Issue Type: Bug
>Reporter: Tom Barber
>Assignee: Tom Barber
>  Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their 
> own set of configuration files and locations. This is complex to manage and 
> causes additional problems when the platform requires distribution across 
> servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an 
> opional Zookeeper module that would allow users to commission a zookeeper 
> cluster and register the various OODT components against it, which will allow 
> the zookeeper cluster to maintain the state of the various OODT components 
> regardless of scale.



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

[jira] [Commented] (OODT-847) New FilemgrMetExtractor to extract File System Attributes

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-847:
-

GitHub user adhulipa opened a pull request:

https://github.com/apache/oodt/pull/42

Fix for OODT-847 contributed by adhulipa & rverma

Implemented FileAttributesExtractor which leverages the Java 7 API to
get file system attributes.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/adhulipa/oodt OODT-847

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/42.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #42


commit ce690461b05da324ce1cb5d480409adec6737737
Author: Aditya Dhulipala 
Date:   2016-10-28T09:36:13Z

Fix for OODT-847 contributed by adhulipa & rverma

Implemented FileAttributesExtractor which leverages the Java 7 API to
get file system attributes.




> New FilemgrMetExtractor to extract File System Attributes
> -
>
> Key: OODT-847
> URL: https://issues.apache.org/jira/browse/OODT-847
> Project: OODT
>  Issue Type: New Feature
>  Components: file manager
>Affects Versions: 0.8.1
>Reporter: Rishi Verma
>Assignee: Rishi Verma
>Priority: Minor
> Fix For: 1.1
>
> Attachments: FileAttributesExtractor.java
>
>
> It's sometimes useful to extract File System metadata from files that people 
> often see when browsing a file on an operating system.
> Examples:
> * POSIX permissions
> * Datetime stamps, including: lastModified, creationTime, lastAccessTime
> * Is a symbolic file?
> * Is a directory?
> * File owner
> * Is hidden file?
> etc.
> Java 7's Files.getAttributes [1] does this in a platform-generic way. We 
> should leverage this and add an extractor for the benefit of the community.
> [1] http://docs.oracle.com/javase/tutorial/essential/io/fileAttr.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-928) Update maven-compiler-plugin from 1.6 to 1.7 in core pom.xml

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-928:
-

Github user asfgit closed the pull request at:

https://github.com/apache/oodt/pull/40


> Update maven-compiler-plugin from 1.6 to 1.7 in core pom.xml
> 
>
> Key: OODT-928
> URL: https://issues.apache.org/jira/browse/OODT-928
> Project: OODT
>  Issue Type: Bug
>  Components: build proces
>Affects Versions: 0.12
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 0.13
>
>
> Right now use of the try-with-resources paradigm introduced within the most 
> recent patch at OODT-927 will break the build due to JDK 1.6 being explicitly 
> specified within the maven-compiler-plugin configuration in core pom.xml.
> The build was running fine for me locally but it seems that it fails on 
> Jenkins due to this which needs to be fixed. PR coming up.
> The issues results in the following
> {code}
> [INFO] [compiler:compile {execution: default-compile}]
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 125 source files to 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/MemoryBasedIngestMapper.java:[53,84]
>  diamond operator is not supported in -source 1.6
>   (use -source 7 or higher to enable diamond operator)
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/DataSourceIngestMapper.java:[70,21]
>  try-with-resources is not supported in -source 1.6
>   (use -source 7 or higher to enable try-with-resources)
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/DataSourceIngestMapper.java:[149,62]
>  diamond operator is not supported in -source 1.6
>   (use -source 7 or higher to enable diamond operator)
> [INFO] 3 errors 
> [INFO] -
> [INFO] 
> 
> [ERROR] BUILD FAILURE
> [INFO] 
> 
> [INFO] Compilation failure
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-928) Update maven-compiler-plugin from 1.6 to 1.7 in core pom.xml

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-928:
-

Github user chrismattmann commented on the issue:

https://github.com/apache/oodt/pull/40
  
+1


> Update maven-compiler-plugin from 1.6 to 1.7 in core pom.xml
> 
>
> Key: OODT-928
> URL: https://issues.apache.org/jira/browse/OODT-928
> Project: OODT
>  Issue Type: Bug
>  Components: build proces
>Affects Versions: 0.12
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 0.13
>
>
> Right now use of the try-with-resources paradigm introduced within the most 
> recent patch at OODT-927 will break the build due to JDK 1.6 being explicitly 
> specified within the maven-compiler-plugin configuration in core pom.xml.
> The build was running fine for me locally but it seems that it fails on 
> Jenkins due to this which needs to be fixed. PR coming up.
> The issues results in the following
> {code}
> [INFO] [compiler:compile {execution: default-compile}]
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 125 source files to 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/MemoryBasedIngestMapper.java:[53,84]
>  diamond operator is not supported in -source 1.6
>   (use -source 7 or higher to enable diamond operator)
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/DataSourceIngestMapper.java:[70,21]
>  try-with-resources is not supported in -source 1.6
>   (use -source 7 or higher to enable try-with-resources)
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/DataSourceIngestMapper.java:[149,62]
>  diamond operator is not supported in -source 1.6
>   (use -source 7 or higher to enable diamond operator)
> [INFO] 3 errors 
> [INFO] -
> [INFO] 
> 
> [ERROR] BUILD FAILURE
> [INFO] 
> 
> [INFO] Compilation failure
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-928) Update maven-compiler-plugin from 1.6 to 1.7 in core pom.xml

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-928:
-

Github user lewismc commented on the issue:

https://github.com/apache/oodt/pull/40
  
Peer review on this one would be appreciated as it will enable us to get 
the builds back to stable.


> Update maven-compiler-plugin from 1.6 to 1.7 in core pom.xml
> 
>
> Key: OODT-928
> URL: https://issues.apache.org/jira/browse/OODT-928
> Project: OODT
>  Issue Type: Bug
>  Components: build proces
>Affects Versions: 0.12
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 0.13
>
>
> Right now use of the try-with-resources paradigm introduced within the most 
> recent patch at OODT-927 will break the build due to JDK 1.6 being explicitly 
> specified within the maven-compiler-plugin configuration in core pom.xml.
> The build was running fine for me locally but it seems that it fails on 
> Jenkins due to this which needs to be fixed. PR coming up.
> The issues results in the following
> {code}
> [INFO] [compiler:compile {execution: default-compile}]
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 125 source files to 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/MemoryBasedIngestMapper.java:[53,84]
>  diamond operator is not supported in -source 1.6
>   (use -source 7 or higher to enable diamond operator)
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/DataSourceIngestMapper.java:[70,21]
>  try-with-resources is not supported in -source 1.6
>   (use -source 7 or higher to enable try-with-resources)
> [ERROR] 
> /home/jenkins/jenkins-slave/workspace/oodt-trunk/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/DataSourceIngestMapper.java:[149,62]
>  diamond operator is not supported in -source 1.6
>   (use -source 7 or higher to enable diamond operator)
> [INFO] 3 errors 
> [INFO] -
> [INFO] 
> 
> [ERROR] BUILD FAILURE
> [INFO] 
> 
> [INFO] Compilation failure
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-928) Update maven-compiler-plugin from 1.6 to 1.7 in core pom.xml

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-928:
-

GitHub user lewismc opened a pull request:

https://github.com/apache/oodt/pull/40

OODT-928 Update maven-compiler-plugin from 1.6 to 1.7 in core pom.xml

This issue addresses https://issues.apache.org/jira/browse/OODT-928

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lewismc/oodt OODT-928

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/40.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #40


commit 2e5d9785384baf25c03638b0dc386c49ddbeaab7
Author: Lewis John McGibbney 
Date:   2016-06-01T16:51:31Z

OODT-928 Update maven-compiler-plugin from 1.6 to 1.7 in core pom.xml




> Update maven-compiler-plugin from 1.6 to 1.7 in core pom.xml
> 
>
> Key: OODT-928
> URL: https://issues.apache.org/jira/browse/OODT-928
> Project: OODT
>  Issue Type: Bug
>  Components: build proces
>Affects Versions: 0.12
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 0.13
>
>
> Right now use of the try-with-resources paradigm introduced within the most 
> recent patch at OODT-927 will break the build due to JDK 1.6 being explicitly 
> specified within the maven-compiler-plugin configuration in core pom.xml.
> The build was running fine for me locally but it seems that it fails on 
> Jenkins due to this which needs to be fixed. PR coming up.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-927) Values passed to SQL commands should be sanitized in CAS DataSourceIngestMapper.java

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-927:
-

Github user asfgit closed the pull request at:

https://github.com/apache/oodt/pull/39


> Values passed to SQL commands should be sanitized in CAS 
> DataSourceIngestMapper.java
> 
>
> Key: OODT-927
> URL: https://issues.apache.org/jira/browse/OODT-927
> Project: OODT
>  Issue Type: Improvement
>  Components: catalog
>Affects Versions: 0.12
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 0.13
>
>
> Right now in 
> [DataSourceIngestMapper.java|https://github.com/apache/oodt/blob/91d0bafe71124906bd94baad746189caf35fb39c/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/DataSourceIngestMapper.java]
>   values passed to SQL commands are not sanitized. Applications that execute 
> SQL commands should neutralize any externally-provided values used in those 
> commands. Failure to do so could allow an attacker to include input that 
> changes the query so that unintended commands are executed, or sensitive data 
> is exposed.
> This issue checks that method parameters are not used directly in 
> non-Hibernate SQL statements, and that parameter binding, rather than 
> concatenation is used in Hibernate statements.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-927) Values passed to SQL commands should be sanitized in CAS DataSourceIngestMapper.java

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-927:
-

Github user chrismattmann commented on the pull request:

https://github.com/apache/oodt/pull/39
  
+1 to merge @lewismc 


> Values passed to SQL commands should be sanitized in CAS 
> DataSourceIngestMapper.java
> 
>
> Key: OODT-927
> URL: https://issues.apache.org/jira/browse/OODT-927
> Project: OODT
>  Issue Type: Improvement
>  Components: catalog
>Affects Versions: 0.12
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 0.13
>
>
> Right now in 
> [DataSourceIngestMapper.java|https://github.com/apache/oodt/blob/91d0bafe71124906bd94baad746189caf35fb39c/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/DataSourceIngestMapper.java]
>   values passed to SQL commands are not sanitized. Applications that execute 
> SQL commands should neutralize any externally-provided values used in those 
> commands. Failure to do so could allow an attacker to include input that 
> changes the query so that unintended commands are executed, or sensitive data 
> is exposed.
> This issue checks that method parameters are not used directly in 
> non-Hibernate SQL statements, and that parameter binding, rather than 
> concatenation is used in Hibernate statements.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-927) Values passed to SQL commands should be sanitized in CAS DataSourceIngestMapper.java

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-927:
-

Github user lewismc commented on the pull request:

https://github.com/apache/oodt/pull/39
  
Any comments folks?


> Values passed to SQL commands should be sanitized in CAS 
> DataSourceIngestMapper.java
> 
>
> Key: OODT-927
> URL: https://issues.apache.org/jira/browse/OODT-927
> Project: OODT
>  Issue Type: Improvement
>  Components: catalog
>Affects Versions: 0.12
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 0.13
>
>
> Right now in 
> [DataSourceIngestMapper.java|https://github.com/apache/oodt/blob/91d0bafe71124906bd94baad746189caf35fb39c/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/DataSourceIngestMapper.java]
>   values passed to SQL commands are not sanitized. Applications that execute 
> SQL commands should neutralize any externally-provided values used in those 
> commands. Failure to do so could allow an attacker to include input that 
> changes the query so that unintended commands are executed, or sensitive data 
> is exposed.
> This issue checks that method parameters are not used directly in 
> non-Hibernate SQL statements, and that parameter binding, rather than 
> concatenation is used in Hibernate statements.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-927) Values passed to SQL commands should be sanitized in CAS DataSourceIngestMapper.java

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-927:
-

GitHub user lewismc opened a pull request:

https://github.com/apache/oodt/pull/39

OODT-927 Values passed to SQL commands should be sanitized in CAS 
DataSourceIngestMapper.java

Hi Folks,
This PR 
 * uses prepared statements for SQL queries
 * sanitizes the variable inputs
 * implements try-with-resources if blocks for efficiency which were 
introduced in Java 7
 * makes commonly used strings static final string constants
 * uses @Override explicitly
 * adds a wee bit of formatting to core/pom.xml so that Tom's formatting 
job is not buggered.

Generally speaking this cuts down on a alot of code, simplifies things and 
make it more modern across the concerned package.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lewismc/oodt master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/39.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #39


commit 1a1cdf1ac8e3dc48187f66923ffd6baa92ced3c3
Author: Lewis John McGibbney 
Date:   2016-05-26T21:25:25Z

OODT-927 Values passed to SQL commands should be sanitized in CAS 
DataSourceIngestMapper.java




> Values passed to SQL commands should be sanitized in CAS 
> DataSourceIngestMapper.java
> 
>
> Key: OODT-927
> URL: https://issues.apache.org/jira/browse/OODT-927
> Project: OODT
>  Issue Type: Improvement
>  Components: catalog
>Affects Versions: 0.12
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Critical
> Fix For: 0.13
>
>
> Right now in 
> [DataSourceIngestMapper.java|https://github.com/apache/oodt/blob/91d0bafe71124906bd94baad746189caf35fb39c/catalog/src/main/java/org/apache/oodt/cas/catalog/mapping/DataSourceIngestMapper.java]
>   values passed to SQL commands are not sanitized. Applications that execute 
> SQL commands should neutralize any externally-provided values used in those 
> commands. Failure to do so could allow an attacker to include input that 
> changes the query so that unintended commands are executed, or sensitive data 
> is exposed.
> This issue checks that method parameters are not used directly in 
> non-Hibernate SQL statements, and that parameter binding, rather than 
> concatenation is used in Hibernate statements.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-925) Update schema.xml field definitions for SOLR 5.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-925:
-

Github user asfgit closed the pull request at:

https://github.com/apache/oodt/pull/38


> Update schema.xml field definitions for SOLR 5.X 
> -
>
> Key: OODT-925
> URL: https://issues.apache.org/jira/browse/OODT-925
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager
>Affects Versions: 0.12
> Environment: Any
>Reporter: Konstantinos Mavrommatis
> Fix For: 0.13
>
>
> Update the File Manager 
> [schema.xml|https://github.com/apache/oodt/blob/master/filemgr/src/main/resources/schema.xml]
>  to match the definitions and requirements of SOLR 5.
> The current version of schema.xml is suitable for the 4.X generation of SOLR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-925) Update schema.xml field definitions for SOLR 5.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-925:
-

Github user chrismattmann commented on the pull request:

https://github.com/apache/oodt/pull/38#issuecomment-207033475
  
+1 from me here to commit thanks @lewismc 


> Update schema.xml field definitions for SOLR 5.X 
> -
>
> Key: OODT-925
> URL: https://issues.apache.org/jira/browse/OODT-925
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager
>Affects Versions: 0.12
> Environment: Any
>Reporter: Konstantinos Mavrommatis
> Fix For: 0.13
>
>
> Update the File Manager 
> [schema.xml|https://github.com/apache/oodt/blob/master/filemgr/src/main/resources/schema.xml]
>  to match the definitions and requirements of SOLR 5.
> The current version of schema.xml is suitable for the 4.X generation of SOLR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-925) Update schema.xml field definitions for SOLR 5.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-925:
-

Github user lewismc closed the pull request at:

https://github.com/apache/oodt/pull/36


> Update schema.xml field definitions for SOLR 5.X 
> -
>
> Key: OODT-925
> URL: https://issues.apache.org/jira/browse/OODT-925
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager
>Affects Versions: 0.12
> Environment: Any
>Reporter: Konstantinos Mavrommatis
> Fix For: 0.13
>
>
> Update the File Manager 
> [schema.xml|https://github.com/apache/oodt/blob/master/filemgr/src/main/resources/schema.xml]
>  to match the definitions and requirements of SOLR 5.
> The current version of schema.xml is suitable for the 4.X generation of SOLR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-925) Update schema.xml field definitions for SOLR 5.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-925:
-

Github user lewismc commented on the pull request:

https://github.com/apache/oodt/pull/36#issuecomment-206502059
  
I screwed this PR up, please refer to https://github.com/apache/oodt/pull/38


> Update schema.xml field definitions for SOLR 5.X 
> -
>
> Key: OODT-925
> URL: https://issues.apache.org/jira/browse/OODT-925
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager
>Affects Versions: 0.12
> Environment: Any
>Reporter: Konstantinos Mavrommatis
> Fix For: 0.13
>
>
> Update the File Manager 
> [schema.xml|https://github.com/apache/oodt/blob/master/filemgr/src/main/resources/schema.xml]
>  to match the definitions and requirements of SOLR 5.
> The current version of schema.xml is suitable for the 4.X generation of SOLR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-925) Update schema.xml field definitions for SOLR 5.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-925:
-

GitHub user lewismc opened a pull request:

https://github.com/apache/oodt/pull/38

OODT-925 Update schema.xml field definitions for SOLR 5.X

This is a new PR for master which addresses 
https://issues.apache.org/jira/browse/OODT-925

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lewismc/oodt master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/oodt/pull/38.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #38


commit 6aadf6780d1dca8d5cc0b08637ba6ffacdb17b86
Author: Lewis John McGibbney 
Date:   2016-03-28T15:09:58Z

OODT-925 Update schema.xml field definitions for SOLR 5.X

commit bcc8420bc9ef3ac5273ea7f62b686742eba74c26
Author: Lewis John McGibbney 
Date:   2016-04-06T17:50:26Z

Merge branch 'OODT-925' of https://github.com/lewismc/oodt

commit a54207f50d2dbc9cd2ef93d137e2531efe386ca3
Author: Lewis John McGibbney 
Date:   2016-04-06T17:54:12Z

OODT-925 Update schema.xml field definitions for SOLR 5.X




> Update schema.xml field definitions for SOLR 5.X 
> -
>
> Key: OODT-925
> URL: https://issues.apache.org/jira/browse/OODT-925
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager
>Affects Versions: 0.12
> Environment: Any
>Reporter: Konstantinos Mavrommatis
> Fix For: 0.13
>
>
> Update the File Manager 
> [schema.xml|https://github.com/apache/oodt/blob/master/filemgr/src/main/resources/schema.xml]
>  to match the definitions and requirements of SOLR 5.
> The current version of schema.xml is suitable for the 4.X generation of SOLR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-925) Update schema.xml field definitions for SOLR 5.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-925:
-

Github user lewismc commented on the pull request:

https://github.com/apache/oodt/pull/36#issuecomment-206393493
  
bq. One question I have - does this maintain back compat with Solr4 schema?

No. I'll resend a PR which achieves this though. Good shout. 


> Update schema.xml field definitions for SOLR 5.X 
> -
>
> Key: OODT-925
> URL: https://issues.apache.org/jira/browse/OODT-925
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager
>Affects Versions: 0.12
> Environment: Any
>Reporter: Konstantinos Mavrommatis
> Fix For: 0.12
>
>
> Update the File Manager 
> [schema.xml|https://github.com/apache/oodt/blob/master/filemgr/src/main/resources/schema.xml]
>  to match the definitions and requirements of SOLR 5.
> The current version of schema.xml is suitable for the 4.X generation of SOLR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-925) Update schema.xml field definitions for SOLR 5.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-925:
-

Github user chrismattmann commented on the pull request:

https://github.com/apache/oodt/pull/36#issuecomment-206390441
  
@lewismc I don't have a Solr5 install, but I am +1 on reviewing the patch 
looks clean. One question I have - does this maintain back compat with Solr4 
schema? If not, I'd like us to keep a schema4.xml and schema5.xml file. Make 
sense?


> Update schema.xml field definitions for SOLR 5.X 
> -
>
> Key: OODT-925
> URL: https://issues.apache.org/jira/browse/OODT-925
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager
>Affects Versions: 0.12
> Environment: Any
>Reporter: Konstantinos Mavrommatis
> Fix For: 0.12
>
>
> Update the File Manager 
> [schema.xml|https://github.com/apache/oodt/blob/master/filemgr/src/main/resources/schema.xml]
>  to match the definitions and requirements of SOLR 5.
> The current version of schema.xml is suitable for the 4.X generation of SOLR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-925) Update schema.xml field definitions for SOLR 5.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-925:
-

Github user lewismc commented on the pull request:

https://github.com/apache/oodt/pull/36#issuecomment-206345429
  
Anyone able to test this patch out?


> Update schema.xml field definitions for SOLR 5.X 
> -
>
> Key: OODT-925
> URL: https://issues.apache.org/jira/browse/OODT-925
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager
>Affects Versions: 0.12
> Environment: Any
>Reporter: Konstantinos Mavrommatis
> Fix For: 0.12
>
>
> Update the File Manager 
> [schema.xml|https://github.com/apache/oodt/blob/master/filemgr/src/main/resources/schema.xml]
>  to match the definitions and requirements of SOLR 5.
> The current version of schema.xml is suitable for the 4.X generation of SOLR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-926) Sync pom.xml versioning

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-926:
-

Github user asfgit closed the pull request at:

https://github.com/apache/oodt/pull/37


> Sync pom.xml versioning
> ---
>
> Key: OODT-926
> URL: https://issues.apache.org/jira/browse/OODT-926
> Project: OODT
>  Issue Type: Bug
>  Components: build proces
>Affects Versions: 0.12
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 0.13
>
>
> As per http://www.mail-archive.com/dev%40oodt.apache.org/msg06706.html it 
> seems that pom.xml versions have become out of sync on master branch. They 
> should be consistent and pegged to 0.13-SNAPSHOT as of writing



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-926) Sync pom.xml versioning

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-926:
-

Github user buggtb commented on the pull request:

https://github.com/apache/oodt/pull/37#issuecomment-205715756
  
Commit away!


> Sync pom.xml versioning
> ---
>
> Key: OODT-926
> URL: https://issues.apache.org/jira/browse/OODT-926
> Project: OODT
>  Issue Type: Bug
>  Components: build proces
>Affects Versions: 0.12
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 0.13
>
>
> As per http://www.mail-archive.com/dev%40oodt.apache.org/msg06706.html it 
> seems that pom.xml versions have become out of sync on master branch. They 
> should be consistent and pegged to 0.13-SNAPSHOT as of writing



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-925) Update schema.xml field definitions for SOLR 5.X

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-925:
-

Github user lewismc commented on the pull request:

https://github.com/apache/oodt/pull/36#issuecomment-205691424
  
Any objections to commit?


> Update schema.xml field definitions for SOLR 5.X 
> -
>
> Key: OODT-925
> URL: https://issues.apache.org/jira/browse/OODT-925
> Project: OODT
>  Issue Type: Improvement
>  Components: file manager
>Affects Versions: 0.12
> Environment: Any
>Reporter: Konstantinos Mavrommatis
> Fix For: 0.12
>
>
> Update the File Manager 
> [schema.xml|https://github.com/apache/oodt/blob/master/filemgr/src/main/resources/schema.xml]
>  to match the definitions and requirements of SOLR 5.
> The current version of schema.xml is suitable for the 4.X generation of SOLR



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OODT-926) Sync pom.xml versioning

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on OODT-926:
-

Github user lewismc commented on the pull request:

https://github.com/apache/oodt/pull/37#issuecomment-205691368
  
Any objections to commit?


> Sync pom.xml versioning
> ---
>
> Key: OODT-926
> URL: https://issues.apache.org/jira/browse/OODT-926
> Project: OODT
>  Issue Type: Bug
>  Components: build proces
>Affects Versions: 0.12
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
> Fix For: 0.13
>
>
> As per http://www.mail-archive.com/dev%40oodt.apache.org/msg06706.html it 
> seems that pom.xml versions have become out of sync on master branch. They 
> should be consistent and pegged to 0.13-SNAPSHOT as of writing



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)