[jira] [Resolved] (OODT-973) Update mvn/archetypes/radix module script templates to remove ghost PID files
[
https://issues.apache.org/jira/browse/OODT-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-973.
Resolution: Fixed
thanks [~ThejanWijesinghe]
{noformat}
nonas:oodt mattmann$ git push -u origin master
Counting objects: 32, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (28/28), done.
Writing objects: 100% (32/32), 3.20 KiB | 1.07 MiB/s, done.
Total 32 (delta 9), reused 0 (delta 0)
remote: oodt git commit: Record changes for OODT-973 Update
mvn/archetypes/radix module script templates to remove ghost PID files
contributed by ThejanW.
remote: oodt git commit: Merge branch 'pid-bug' of
https://github.com/ThejanW/oodt into OODT-973
remote: oodt git commit: update filemgr, wmgr & resmgr scripts
To https://git-wip-us.apache.org/repos/asf/oodt.git
8b4a3d4fe..84af13a93 master -> master
Branch master set up to track remote branch master from origin.
nonas:oodt mattmann${noformat}
> 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] [Assigned] (OODT-973) Update mvn/archetypes/radix module script templates to remove ghost PID files
[ https://issues.apache.org/jira/browse/OODT-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann reassigned OODT-973: -- Assignee: Chris A. Mattmann > 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-868) Integrate Avro RPC with the pcs module
[ https://issues.apache.org/jira/browse/OODT-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404283#comment-16404283 ] Chris A. Mattmann commented on OODT-868: ping [~radu.manole] any interest in working on this? > Integrate Avro RPC with the pcs module > -- > > Key: OODT-868 > URL: https://issues.apache.org/jira/browse/OODT-868 > Project: OODT > Issue Type: Sub-task > Components: pcs >Reporter: Radu Manole >Assignee: Chris A. Mattmann >Priority: Major > Fix For: 1.9 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OODT-868) Integrate Avro RPC with the pcs module
[ https://issues.apache.org/jira/browse/OODT-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378062#comment-16378062 ] Chris A. Mattmann commented on OODT-868: [~radu.manole] would you have any time to finish this out? > Integrate Avro RPC with the pcs module > -- > > Key: OODT-868 > URL: https://issues.apache.org/jira/browse/OODT-868 > Project: OODT > Issue Type: Sub-task > Components: pcs >Reporter: Radu Manole >Assignee: Chris A. Mattmann >Priority: Major > Fix For: 1.9 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OODT-969) Tests for Avro File Manager client and server
[
https://issues.apache.org/jira/browse/OODT-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-969.
Resolution: Fixed
* fixed, thanks Imesha!
{noformat}
nonas:oodt mattmann$ git push -u origin master
Counting objects: 45, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (34/34), done.
Writing objects: 100% (45/45), 13.34 KiB | 2.22 MiB/s, done.
Total 45 (delta 20), reused 0 (delta 0)
rm -rf *remote: oodt git commit: record changes for OODT-969 and OODT-970:
Netty Transceiver throws an NPE contributed by imesha
remote: oodt git commit: Merge branch 'development' of
https://github.com/IMS94/oodt into development
remote: oodt git commit: Merge branch 'development' of
https://git-wip-us.apache.org/repos/asf/oodt into development
remote: oodt git commit: This fixes [OODT-970] and [OODT-969] - Tests for Avro
File Manager and solve the NPE problem in NettyTransceiver.
remote: oodt git commit: add missing ;
remote: oodt git commit: Fix for OODT-968 Add metadata
remote: oodt git commit: close connection to release client
~*
To https://git-wip-us.apache.org/repos/asf/oodt.git
3af750a5c..ba6ca1b4d master -> master
Branch master set up to track remote branch master from origin.
nonas:oodt mattmann${noformat}
> Tests for Avro File Manager client and server
> -
>
> Key: OODT-969
> URL: https://issues.apache.org/jira/browse/OODT-969
> Project: OODT
> Issue Type: Test
> Components: file manager
>Reporter: Imesha Sudasingha
>Assignee: Chris A. Mattmann
>Priority: Blocker
> Fix For: 1.9
>
>
> Avro File Manager requires proper test cases in order to verify its
> functionality. This can easily be done by adapting the test cases from
> XmlRPCFileManager
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OODT-970) Netty Transceiver throws an NPE
[
https://issues.apache.org/jira/browse/OODT-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-970.
Resolution: Fixed
* fixed, thanks Imesha!
{noformat}
nonas:oodt mattmann$ git push -u origin master
Counting objects: 45, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (34/34), done.
Writing objects: 100% (45/45), 13.34 KiB | 2.22 MiB/s, done.
Total 45 (delta 20), reused 0 (delta 0)
rm -rf *remote: oodt git commit: record changes for OODT-969 and OODT-970:
Netty Transceiver throws an NPE contributed by imesha
remote: oodt git commit: Merge branch 'development' of
https://github.com/IMS94/oodt into development
remote: oodt git commit: Merge branch 'development' of
https://git-wip-us.apache.org/repos/asf/oodt into development
remote: oodt git commit: This fixes [OODT-970] and [OODT-969] - Tests for Avro
File Manager and solve the NPE problem in NettyTransceiver.
remote: oodt git commit: add missing ;
remote: oodt git commit: Fix for OODT-968 Add metadata
remote: oodt git commit: close connection to release client
~*
To https://git-wip-us.apache.org/repos/asf/oodt.git
3af750a5c..ba6ca1b4d master -> master
Branch master set up to track remote branch master from origin.
nonas:oodt mattmann${noformat}
> 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] [Assigned] (OODT-970) Netty Transceiver throws an NPE
[
https://issues.apache.org/jira/browse/OODT-970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann reassigned OODT-970:
--
Assignee: Chris A. Mattmann (was: Imesha Sudasingha)
> 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] [Assigned] (OODT-969) Tests for Avro File Manager client and server
[ https://issues.apache.org/jira/browse/OODT-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann reassigned OODT-969: -- Assignee: Chris A. Mattmann (was: Imesha Sudasingha) > Tests for Avro File Manager client and server > - > > Key: OODT-969 > URL: https://issues.apache.org/jira/browse/OODT-969 > Project: OODT > Issue Type: Test > Components: file manager >Reporter: Imesha Sudasingha >Assignee: Chris A. Mattmann >Priority: Blocker > Fix For: 1.9 > > > Avro File Manager requires proper test cases in order to verify its > functionality. This can easily be done by adapting the test cases from > XmlRPCFileManager -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (OODT-950) Condition that compares the same expression
[
https://issues.apache.org/jira/browse/OODT-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann reassigned OODT-950:
--
Assignee: Chris A. Mattmann
> Condition that compares the same expression
> ---
>
> Key: OODT-950
> URL: https://issues.apache.org/jira/browse/OODT-950
> Project: OODT
> Issue Type: Bug
> Components: push pull framework
>Reporter: JC
>Assignee: Chris A. Mattmann
>Priority: Trivial
> Fix For: 1.9
>
>
> Hi
> In a recent Github mirror, I've found the following suspicious code in
> pushpull/src/main/java/org/apache/oodt/cas/pushpull/retrievalsystem/FileRetrievalSystem.java
> {code}
> 662 Protocol modifyAvailableSessionForPath(RemoteSiteFile file)
> 663 throws RemoteConnectionException {
> 664 Protocol session = getAvailableSession();
> 665 if (!file.getSite().getURL().getHost().equals(
> 666 file.getSite().getURL().getHost())
> 667 || !protocolHandler.isProtocolConnected(session)) {
> 668 protocolHandler.disconnect(session);
> 669 session = protocolHandler.getAppropriateProtocol(file, /*
> reuse */
> 670 false, /* navigate */true);
> 671 } else {
> {code}
> In Line 665 and 666, equals compares the same expression. This may not be an
> issue but wanted to report just in case. Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OODT-950) Condition that compares the same expression
[
https://issues.apache.org/jira/browse/OODT-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-950.
Resolution: Fixed
Push Pull is gone, so no need to fix this, thanks [~lifove]
> Condition that compares the same expression
> ---
>
> Key: OODT-950
> URL: https://issues.apache.org/jira/browse/OODT-950
> Project: OODT
> Issue Type: Bug
> Components: push pull framework
>Reporter: JC
>Assignee: Chris A. Mattmann
>Priority: Trivial
> Fix For: 1.9
>
>
> Hi
> In a recent Github mirror, I've found the following suspicious code in
> pushpull/src/main/java/org/apache/oodt/cas/pushpull/retrievalsystem/FileRetrievalSystem.java
> {code}
> 662 Protocol modifyAvailableSessionForPath(RemoteSiteFile file)
> 663 throws RemoteConnectionException {
> 664 Protocol session = getAvailableSession();
> 665 if (!file.getSite().getURL().getHost().equals(
> 666 file.getSite().getURL().getHost())
> 667 || !protocolHandler.isProtocolConnected(session)) {
> 668 protocolHandler.disconnect(session);
> 669 session = protocolHandler.getAppropriateProtocol(file, /*
> reuse */
> 670 false, /* navigate */true);
> 671 } else {
> {code}
> In Line 665 and 666, equals compares the same expression. This may not be an
> issue but wanted to report just in case. Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OODT-951) Wrong null checker
[
https://issues.apache.org/jira/browse/OODT-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-951.
Resolution: Fixed
Thanks [~lifove] appreciate it, that was indeed a bug!
{noformat}
nonas:oodt mattmann$ git commit -m "Fix for OODT-951: Wrong null checker
contributed by JC."
[master 3af750a5c] Fix for OODT-951: Wrong null checker contributed by JC.
2 files changed, 3 insertions(+), 1 deletion(-)
nonas:oodt mattmann$ git push -u origin master
Counting objects: 14, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (9/9), done.
Writing objects: 100% (14/14), 1000 bytes | 500.00 KiB/s, done.
Total 14 (delta 6), reused 0 (delta 0)
remote: oodt git commit: Fix for OODT-951: Wrong null checker contributed by JC.
To https://git-wip-us.apache.org/repos/asf/oodt.git
9e5d75d5e..3af750a5c master -> master
Branch master set up to track remote branch master from origin.
nonas:oodt mattmann${noformat}
> Wrong null checker
> --
>
> Key: OODT-951
> URL: https://issues.apache.org/jira/browse/OODT-951
> Project: OODT
> Issue Type: Bug
> Components: workflow manager
>Reporter: JC
>Assignee: Chris A. Mattmann
>Priority: Minor
> Fix For: 1.9
>
>
> Hi
> In a recent Github snapshot, I've found a following code smell.
> Path:
> workflow/src/main/java/org/apache/oodt/cas/workflow/engine/PrioritizedQueueBasedWorkflowEngine.java
> {code}
> 69 public PrioritizedQueueBasedWorkflowEngine(WorkflowInstanceRepository
> repo,
> 70 PrioritySorter prioritizer, WorkflowLifecycleManager lifecycle,
> 71 EngineRunner runner, WorkflowRepository modelRepo, long
> querierWaitSeconds) {
> 72 this.repo = repo;
> 73 this.prioritizer = prioritizer != null ? new
> HighestFIFOPrioritySorter(1,
> 74 50, 1) : prioritizer;
> 75 this.lifecycle = lifecycle;
> 76 this.modelRepo = modelRepo;
> {code}
> In Line 73, prioritizer != null should be prioritizer == null? This might be
> a trivial issue but wanted to report just in case.
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OODT-951) Wrong null checker
[
https://issues.apache.org/jira/browse/OODT-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann reassigned OODT-951:
--
Assignee: Chris A. Mattmann
> Wrong null checker
> --
>
> Key: OODT-951
> URL: https://issues.apache.org/jira/browse/OODT-951
> Project: OODT
> Issue Type: Bug
> Components: workflow manager
>Reporter: JC
>Assignee: Chris A. Mattmann
>Priority: Minor
> Fix For: 1.9
>
>
> Hi
> In a recent Github snapshot, I've found a following code smell.
> Path:
> workflow/src/main/java/org/apache/oodt/cas/workflow/engine/PrioritizedQueueBasedWorkflowEngine.java
> {code}
> 69 public PrioritizedQueueBasedWorkflowEngine(WorkflowInstanceRepository
> repo,
> 70 PrioritySorter prioritizer, WorkflowLifecycleManager lifecycle,
> 71 EngineRunner runner, WorkflowRepository modelRepo, long
> querierWaitSeconds) {
> 72 this.repo = repo;
> 73 this.prioritizer = prioritizer != null ? new
> HighestFIFOPrioritySorter(1,
> 74 50, 1) : prioritizer;
> 75 this.lifecycle = lifecycle;
> 76 this.modelRepo = modelRepo;
> {code}
> In Line 73, prioritizer != null should be prioritizer == null? This might be
> a trivial issue but wanted to report just in case.
> Thanks!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (OODT-960) upgrade spring
[ https://issues.apache.org/jira/browse/OODT-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-960. Resolution: Fixed no fix version and too generic > upgrade spring > -- > > Key: OODT-960 > URL: https://issues.apache.org/jira/browse/OODT-960 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Assignee: Tom Barber >Priority: Major > > Spring 2.5.4 has a bunch of CVE's against it, we should update it to a newer > version -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OODT-959) Update tika
[ https://issues.apache.org/jira/browse/OODT-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-959. Resolution: Fixed no fix version and too generic > Update tika > --- > > Key: OODT-959 > URL: https://issues.apache.org/jira/browse/OODT-959 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OODT-961) update httpclient
[ https://issues.apache.org/jira/browse/OODT-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-961. Resolution: Fixed no fix version and too generic > update httpclient > -- > > Key: OODT-961 > URL: https://issues.apache.org/jira/browse/OODT-961 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Assignee: Tom Barber >Priority: Major > > Fix a potential MiM attack -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OODT-962) upgrade pdfbox
[ https://issues.apache.org/jira/browse/OODT-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-962. Resolution: Fixed no fix version and too generic > upgrade pdfbox > --- > > Key: OODT-962 > URL: https://issues.apache.org/jira/browse/OODT-962 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Assignee: Tom Barber >Priority: Major > > Fix a potential PDF based attack -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OODT-968) add metadata removes product
[ https://issues.apache.org/jira/browse/OODT-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated OODT-968: --- Component/s: file manager > add metadata removes product > > > Key: OODT-968 > URL: https://issues.apache.org/jira/browse/OODT-968 > Project: OODT > Issue Type: Bug > Components: file manager >Reporter: Tom Barber >Assignee: Chris A. Mattmann >Priority: Major > Fix For: 1.2.2 > > > in 1.2 if I add metadata it removes the product and doesn't complete the task -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OODT-968) add metadata removes product
[ https://issues.apache.org/jira/browse/OODT-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-968. Resolution: Fixed > add metadata removes product > > > Key: OODT-968 > URL: https://issues.apache.org/jira/browse/OODT-968 > Project: OODT > Issue Type: Bug > Components: file manager >Reporter: Tom Barber >Assignee: Chris A. Mattmann >Priority: Major > Fix For: 1.2.2 > > > in 1.2 if I add metadata it removes the product and doesn't complete the task -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (OODT-968) add metadata removes product
[ https://issues.apache.org/jira/browse/OODT-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann reopened OODT-968: Assignee: Chris A. Mattmann (was: Tom Barber) > add metadata removes product > > > Key: OODT-968 > URL: https://issues.apache.org/jira/browse/OODT-968 > Project: OODT > Issue Type: Bug >Reporter: Tom Barber >Assignee: Chris A. Mattmann >Priority: Major > Fix For: 1.2.2 > > > in 1.2 if I add metadata it removes the product and doesn't complete the task -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OODT-968) add metadata removes product
[ https://issues.apache.org/jira/browse/OODT-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated OODT-968: --- Fix Version/s: 1.2.2 > add metadata removes product > > > Key: OODT-968 > URL: https://issues.apache.org/jira/browse/OODT-968 > Project: OODT > Issue Type: Bug >Reporter: Tom Barber >Assignee: Chris A. Mattmann >Priority: Major > Fix For: 1.2.2 > > > in 1.2 if I add metadata it removes the product and doesn't complete the task -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OODT-971) Default filemgr.properties is buggy in radix post AvroRPC
[
https://issues.apache.org/jira/browse/OODT-971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann updated OODT-971:
---
Fix Version/s: (was: 1.2.1)
1.9
> Default filemgr.properties is buggy in radix post AvroRPC
> -
>
> Key: OODT-971
> URL: https://issues.apache.org/jira/browse/OODT-971
> Project: OODT
> Issue Type: Bug
> Components: file manager, radix
>Affects Versions: 1.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.9
>
>
> When a user creates and builds a new Radix distribution, the
> filemgr.properties references such as
> {code}
> # xml rpc client configuration
> org.apache.oodt.cas.filemgr.system.xmlrpc.connectionTimeout.minutes=20
> org.apache.oodt.cas.filemgr.system.xmlrpc.requestTimeout.minutes=60
> #org.apache.oodt.cas.filemgr.system.xmlrpc.connection.retries=0
> #org.apache.oodt.cas.filemgr.system.xmlrpc.connection.retry.interval.seconds=3
> {code}
> Although these are _fine_ e.g. they still work, the package naming is now off
> as there is no package actually named
> {code}
> org.apache.oodt.cas.filemgr.system.xmlrpc...
> {code}
> The only issue I have with changing this important configuration setting, is
> that is would essentially be backwards non-compatible with EVERY OODT install
> unless your new install was powered by Radix.
> Any comments as to what to do? I am happy to close this as *wont fix* due to
> the backwards non-compatible nature of a proposed fix which would _correct_
> the package naming but I just wanted to post for consideration here folks. I
> will open a new issue regarding adding AvroRPC filemgr configuration in a
> separate issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OODT-971) Default filemgr.properties is buggy in radix post AvroRPC
[
https://issues.apache.org/jira/browse/OODT-971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16375736#comment-16375736
]
Chris A. Mattmann commented on OODT-971:
My suggestions on list discussed on list:
# 2.0-master and post - only AvroRPC
# 1.9-master supports AvroRPC and last release supporting XML-RPC
Given that, I think in 2.0 master, we should make the RADIX file match the Avro
and take out XML-RPC. In 1.9-master (current) we don't need to worry about it.
> Default filemgr.properties is buggy in radix post AvroRPC
> -
>
> Key: OODT-971
> URL: https://issues.apache.org/jira/browse/OODT-971
> Project: OODT
> Issue Type: Bug
> Components: file manager, radix
>Affects Versions: 1.2
>Reporter: Lewis John McGibbney
>Assignee: Lewis John McGibbney
>Priority: Major
> Fix For: 1.2.1
>
>
> When a user creates and builds a new Radix distribution, the
> filemgr.properties references such as
> {code}
> # xml rpc client configuration
> org.apache.oodt.cas.filemgr.system.xmlrpc.connectionTimeout.minutes=20
> org.apache.oodt.cas.filemgr.system.xmlrpc.requestTimeout.minutes=60
> #org.apache.oodt.cas.filemgr.system.xmlrpc.connection.retries=0
> #org.apache.oodt.cas.filemgr.system.xmlrpc.connection.retry.interval.seconds=3
> {code}
> Although these are _fine_ e.g. they still work, the package naming is now off
> as there is no package actually named
> {code}
> org.apache.oodt.cas.filemgr.system.xmlrpc...
> {code}
> The only issue I have with changing this important configuration setting, is
> that is would essentially be backwards non-compatible with EVERY OODT install
> unless your new install was powered by Radix.
> Any comments as to what to do? I am happy to close this as *wont fix* due to
> the backwards non-compatible nature of a proposed fix which would _correct_
> the package naming but I just wanted to post for consideration here folks. I
> will open a new issue regarding adding AvroRPC filemgr configuration in a
> separate issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OODT-972) Add filemgr.server and filemgr.client configuration keys to Radix filemgr.properties
[
https://issues.apache.org/jira/browse/OODT-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374702#comment-16374702
]
Chris A. Mattmann commented on OODT-972:
Fixed:
{noformat}
nonas:oodt mattmann$ git push -u origin master
Counting objects: 17, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (15/15), done.
Writing objects: 100% (17/17), 1.65 KiB | 843.00 KiB/s, done.
Total 17 (delta 6), reused 0 (delta 0)
remote: oodt git commit: Merge branch 'master' into OODT-972
remote: oodt git commit: OODT-972 Add filemgr.server and filemgr.client
configuration keys to Radix filemgr.properties
To https://git-wip-us.apache.org/repos/asf/oodt.git
33d64a6dc..9e5d75d5e master -> master
Branch master set up to track remote branch master from origin.
nonas:oodt mattmann${noformat}
> 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: Chris A. Mattmann
>Priority: Major
> Fix For: 1.9
>
>
> 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] [Resolved] (OODT-972) Add filemgr.server and filemgr.client configuration keys to Radix filemgr.properties
[
https://issues.apache.org/jira/browse/OODT-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-972.
Resolution: Fixed
Fix Version/s: (was: 1.2.1)
1.9
Committed to Master!
{noformat}
nonas:oodt mattmann$ git commit -m "Record change for OODT-972; bring 1.2.2
release changes in. Change current master to 1.9"
[master 33d64a6dc] Record change for OODT-972; bring 1.2.2 release changes in.
Change current master to 1.9
1 file changed, 12 insertions(+), 1 deletion(-)
nonas:oodt mattmann$ git push -u origin master
Counting objects: 3, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 528 bytes | 528.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: oodt git commit: Record change for OODT-972; bring 1.2.2 release
changes in. Change current master to 1.9
To https://git-wip-us.apache.org/repos/asf/oodt.git
13d41767a..33d64a6dc master -> master
Branch master set up to track remote branch master from origin.
nonas:oodt mattmann${noformat}
> 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: Chris A. Mattmann
>Priority: Major
> Fix For: 1.9
>
>
> 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] [Assigned] (OODT-972) Add filemgr.server and filemgr.client configuration keys to Radix filemgr.properties
[ https://issues.apache.org/jira/browse/OODT-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann reassigned OODT-972: -- Assignee: Chris A. Mattmann (was: Lewis John McGibbney) > 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: Chris A. Mattmann >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] [Resolved] (OODT-967) Solr version for 1.2.1 breaks SolrDumper in File Manager
[ https://issues.apache.org/jira/browse/OODT-967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-967. Resolution: Fixed Fix for OODT-967 Solr version for 1.2.1 breaks SolrDumper in File Manager Project: http://git-wip-us.apache.org/repos/asf/oodt/repo Commit: http://git-wip-us.apache.org/repos/asf/oodt/commit/02dac40e Tree: http://git-wip-us.apache.org/repos/asf/oodt/tree/02dac40e Diff: http://git-wip-us.apache.org/repos/asf/oodt/diff/02dac40e Branch: refs/heads/OODT-967 Commit: 02dac40e43a13b2ba16ded33cf0e770058dc4cda Parents: 3105f9d Author: Chris Mattmann Authored: Fri Nov 10 17:51:28 2017 -0800 Committer: Chris Mattmann Committed: Fri Nov 10 17:51:28 2017 -0800 > Solr version for 1.2.1 breaks SolrDumper in File Manager > > > Key: OODT-967 > URL: https://issues.apache.org/jira/browse/OODT-967 > Project: OODT > Issue Type: Bug > Components: file manager >Affects Versions: 1.2 > Environment: DRAT, SolrIndexer >Reporter: Chris A. Mattmann >Assignee: Chris A. Mattmann > Fix For: 1.2.1 > > > As described here: https://github.com/apache/drat/issues/101 Apache OODT 1.2 > was released with a pinned Solrj version 6.2.1, which is incompatible with > the SolrIndexer since it expects to talk to a pinned OODT Solr 4.2.1 webapp. > The prior version of Solrj, 1.3.0, worked fine. Apache OODT 1.2.1 will > release this hot fix which renders SolrIndexer usable again. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (OODT-967) Solr version for 1.2.1 breaks SolrDumper in File Manager
Chris A. Mattmann created OODT-967: -- Summary: Solr version for 1.2.1 breaks SolrDumper in File Manager Key: OODT-967 URL: https://issues.apache.org/jira/browse/OODT-967 Project: OODT Issue Type: Bug Components: file manager Affects Versions: 1.2 Environment: DRAT, SolrIndexer Reporter: Chris A. Mattmann Assignee: Chris A. Mattmann Fix For: 1.2.1 As described here: https://github.com/apache/drat/issues/101 Apache OODT 1.2 was released with a pinned Solrj version 6.2.1, which is incompatible with the SolrIndexer since it expects to talk to a pinned OODT Solr 4.2.1 webapp. The prior version of Solrj, 1.3.0, worked fine. Apache OODT 1.2.1 will release this hot fix which renders SolrIndexer usable again. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OODT-966) agility broken syntax under Python 3.X
[
https://issues.apache.org/jira/browse/OODT-966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann updated OODT-966:
---
Fix Version/s: 1.9
> 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
(v6.4.14#64029)
[jira] [Resolved] (OODT-869) Integrate Avro RPC with the commons module
[ https://issues.apache.org/jira/browse/OODT-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-869. Resolution: Fixed committed referenced WIP > Integrate Avro RPC with the commons module > -- > > Key: OODT-869 > URL: https://issues.apache.org/jira/browse/OODT-869 > Project: OODT > Issue Type: Sub-task > Components: commons >Reporter: Radu Manole >Assignee: Chris A. Mattmann > Fix For: 1.9 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-933) @Deprecate all XMLRPC Code
[
https://issues.apache.org/jira/browse/OODT-933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-933.
Resolution: Fixed
- done!
{noformat}
To https://git-wip-us.apache.org/repos/asf/oodt.git
444a5a997..5794ec3bc development -> development
Branch development set up to track remote branch development from origin.
nonas:oodt mattmann$ git checkout master
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.
nonas:oodt mattmann$ git merge development
Updating d26d33cd9..5794ec3bc
Fast-forward
commons/src/main/java/org/apache/oodt/commons/ExecServer.java
| 2 ++
commons/src/main/java/org/apache/oodt/commons/util/XMLRPC.java
| 2 ++
crawler/src/main/java/org/apache/oodt/cas/crawl/daemon/CrawlDaemon.java
| 3 ++-
crawler/src/main/java/org/apache/oodt/cas/crawl/daemon/CrawlDaemonController.java
| 3 ++-
filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/XmlRpcFileManager.java
| 2 ++
filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/XmlRpcFileManagerClient.java
| 2 ++
filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/XmlRpcFileManagerServer.java
| 4
filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/rpc/XmlRpcFileManagerClientFactory.java
| 2 +-
filemgr/src/main/java/org/apache/oodt/cas/filemgr/system/rpc/XmlRpcFileManagerServerFactory.java
| 1 +
filemgr/src/main/java/org/apache/oodt/cas/filemgr/util/XmlRpcStructFactory.java
| 1 +
filemgr/src/main/java/org/apache/oodt/cas/filemgr/util/XmlStructFactory.java
| 1 +
resource/src/main/java/org/apache/oodt/cas/resource/system/XmlRpcResourceManager.java
| 3 ++-
resource/src/main/java/org/apache/oodt/cas/resource/system/XmlRpcResourceManagerClient.java
| 3 ++-
resource/src/main/java/org/apache/oodt/cas/resource/system/extern/XmlRpcBatchStub.java
| 3 ++-
workflow/src/main/java/org/apache/oodt/cas/workflow/system/XmlRpcWorkflowManager.java
| 2 ++
workflow/src/main/java/org/apache/oodt/cas/workflow/system/XmlRpcWorkflowManagerClient.java
| 3 ++-
workflow/src/main/java/org/apache/oodt/cas/workflow/system/rpc/XmlRpcWorkflowManagerFactory.java
| 4
17 files changed, 34 insertions(+), 7 deletions(-)
nonas:oodt mattmann$ git push -u origin master
Total 0 (delta 0), reused 0 (delta 0)
remote: oodt git commit: Merge OODT-933: Deprecate all XMLRPC code.
remote: oodt git commit: OODT-933 marked code that uses XMLRPC
To https://git-wip-us.apache.org/repos/asf/oodt.git
d26d33cd9..5794ec3bc master -> master
Branch master set up to track remote branch master from origin.
{noformat}
> @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] [Resolved] (OODT-867) Integrate Avro RPC with the resource module
[ https://issues.apache.org/jira/browse/OODT-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-867. Resolution: Fixed - done > Integrate Avro RPC with the resource module > --- > > Key: OODT-867 > URL: https://issues.apache.org/jira/browse/OODT-867 > Project: OODT > Issue Type: Sub-task > Components: resource manager >Reporter: Radu Manole >Assignee: Chris A. Mattmann > Fix For: 1.9 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OODT-956) Add connection checks to components
[ https://issues.apache.org/jira/browse/OODT-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated OODT-956: --- Fix Version/s: (was: 1.2) 1.3 > Add connection checks to components > --- > > Key: OODT-956 > URL: https://issues.apache.org/jira/browse/OODT-956 > Project: OODT > Issue Type: Bug >Affects Versions: 1.1 >Reporter: Tom Barber > Fix For: 1.3 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OODT-964) AvroRpcWorkflowManageTest fails due to NPE
[ https://issues.apache.org/jira/browse/OODT-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated OODT-964: --- Fix Version/s: 1.3 > AvroRpcWorkflowManageTest fails due to NPE > -- > > Key: OODT-964 > URL: https://issues.apache.org/jira/browse/OODT-964 > Project: OODT > Issue Type: Bug > Components: workflow manager >Affects Versions: 1.2 >Reporter: Imesha Sudasingha >Assignee: Imesha Sudasingha > Fix For: 1.3 > > > *org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager* tes fails > due to a NPE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-963) Workflow Manager Tests fail due to ZK-config feature
[
https://issues.apache.org/jira/browse/OODT-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-963.
Resolution: Fixed
Fix Version/s: 1.3
Great work [~imesha]!
{noformat}
[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.3-SNAPSHOT/oodt-1.3-SNAPSHOT.pom
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] OODT Core .. SUCCESS [ 2.089 s]
[INFO] Common Utilities ... SUCCESS [ 23.410 s]
[INFO] CAS Command Line Interface . SUCCESS [ 8.908 s]
[INFO] OODT - Configuration Management SUCCESS [ 24.494 s]
[INFO] Process Control System Input Data Package .. SUCCESS [ 1.604 s]
[INFO] Catalog and Archive Service Generic Multi-valued Metadata Container
SUCCESS [ 2.893 s]
[INFO] Catalog and Archive File Management Component .. SUCCESS [03:17 min]
[INFO] Catalog and Archive Resource Management Component .. SUCCESS [ 19.712 s]
[INFO] Catalog and Archive Workflow Management Component .. SUCCESS [ 34.483 s]
[INFO] Catalog and Archive Crawling Framework . SUCCESS [ 28.783 s]
[INFO] OODT CAS Curator Single Sign On Security Package ... SUCCESS [ 1.913 s]
[INFO] CAS Curation Web Services .. SUCCESS [ 10.401 s]
[INFO] Process Control System Core Package SUCCESS [ 19.273 s]
[INFO] OODT Wicket Web Components . SUCCESS [ 4.770 s]
[INFO] CAS Curation Interface . SUCCESS [ 10.254 s]
[INFO] CAS PGE Adaptor Framework .. SUCCESS [ 22.754 s]
[INFO] CAS Installer Maven Mojo ... SUCCESS [ 3.097 s]
[INFO] OODT :: Archetypes :: OpsUI SUCCESS [ 1.194 s]
[INFO] OODT :: Archetypes :: RADiX SUCCESS [ 1.341 s]
[INFO] OODT :: Archetypes . SUCCESS [ 0.033 s]
[INFO] CAS File Manager Browser Web App ... SUCCESS [ 8.492 s]
[INFO] CAS Workflow Manager Monitor Web App ... SUCCESS [ 5.006 s]
[INFO] CAS Product Server Web Application . SUCCESS [ 13.420 s]
[INFO] CAS Workflow REST Services . SUCCESS [ 4.638 s]
[INFO] Process Control System Operator Interface Webapp ... SUCCESS [ 19.873 s]
[INFO] OODT Process Control System JAX-RS service layer ... SUCCESS [ 8.082 s]
[INFO] Apache OODT SUCCESS [ 0.040 s]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 07:58 min
[INFO] Finished at: 2017-10-12T10:28:04-07:00
[INFO] Final Memory: 123M/1584M
[INFO]
nonas:oodt mattmann$ git push -u origin development
Username for 'https://git-wip-us.apache.org': mattmann
Password for 'https://mattm...@git-wip-us.apache.org':
Counting objects: 83, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (60/60), done.
Writing objects: 100% (83/83), 6.43 KiB | 1.29 MiB/s, done.
Total 83 (delta 30), reused 0 (delta 0)
remote: oodt git commit: Fix merge conflict.
remote: oodt git commit: [OODT-964] Removed empty test/workflow.properties
which caused wmgr tests fail
remote: oodt git commit: Merge branch 'feature/zookeeper-config' of
https://github.com/IMS94/oodt into development
remote: oodt git commit: Improved java docs
remote: oodt git commit: [OODT-965] Added configuration change listening feature
remote: oodt git commit: [OODT-963] Fixed surefire test failures in workflow
manager due to forkMode
remote: oodt git commit: Merge branch 'feature/zookeeper-config' into
development
remote: oodt git commit: Improved java docs
remote: oodt git commit: Added configuration change listening feature
To https://git-wip-us.apache.org/repos/asf/oodt.git
ce89ad12b..444a5a997 development -> development
Branch development set up to track remote branch development from origin.
nonas:oodt mattmann$
{noformat}
> 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
> Fix For: 1.3
>
>
> Following errors occur when running the tests related to the workflow manager:
> [https://paste.apache.org/Vd4a]
>
[jira] [Resolved] (OODT-964) AvroRpcWorkflowManageTest fails due to NPE
[ https://issues.apache.org/jira/browse/OODT-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-964. Resolution: Fixed > AvroRpcWorkflowManageTest fails due to NPE > -- > > Key: OODT-964 > URL: https://issues.apache.org/jira/browse/OODT-964 > Project: OODT > Issue Type: Bug > Components: workflow manager >Affects Versions: 1.2 >Reporter: Imesha Sudasingha >Assignee: Imesha Sudasingha > > *org.apache.oodt.cas.workflow.system.TestAvroRpcWorkflowManager* tes fails > due to a NPE -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OODT-963) Workflow Manager Tests fail due to ZK-config feature
[ https://issues.apache.org/jira/browse/OODT-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann reassigned OODT-963: -- Assignee: Chris A. Mattmann (was: Imesha Sudasingha) > 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] [Resolved] (OODT-954) CAS-PGE FileManagerFileStager has NPE b/c it does not set Product Structure
[
https://issues.apache.org/jira/browse/OODT-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-954.
Resolution: Fixed
- addressed:
{noformat}
LMC-053601:oodt mattmann$ git commit -m "Fix for OODT-954: CAS-PGE
FileManagerFileStager has NPE b/c it does not set Product Structure"
[master 44c1555] Fix for OODT-954: CAS-PGE FileManagerFileStager has NPE b/c it
does not set Product Structure
2 files changed, 42 insertions(+)
create mode 100644
pge/src/test/java/org/apache/oodt/cas/pge/staging/TestFileManagerFileStager.java
LMC-053601:oodt mattmann$ git push -u origin master
Counting objects: 25, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (15/15), done.
Writing objects: 100% (25/25), 2.90 KiB | 0 bytes/s, done.
Total 25 (delta 7), reused 0 (delta 0)
remote: oodt git commit: Fix for OODT-954: CAS-PGE FileManagerFileStager has
NPE b/c it does not set Product Structure
remote: oodt git commit: Record change for OODT-954 and include Val's note
about workflow instance rep/Lucene upgrade.
To https://git-wip-us.apache.org/repos/asf/oodt.git
bec179a..44c1555 master -> master
Branch master set up to track remote branch master from origin.
LMC-053601:oodt mattmann$
{noformat}
> CAS-PGE FileManagerFileStager has NPE b/c it does not set Product Structure
> ---
>
> Key: OODT-954
> URL: https://issues.apache.org/jira/browse/OODT-954
> Project: OODT
> Issue Type: Bug
> Components: file manager, pge wrapper framework
>Affects Versions: 1.0
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
>Priority: Blocker
> Fix For: 1.1
>
>
> I found this while testing 1.1 RC #1 - the FileManagerFileStager doesn't set
> the Product.ProductStructure property causing it to be inoperable for use in
> File Staging. I'll contribute a quick fix and unit test shortly for it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (OODT-954) CAS-PGE FileManagerFileStager has NPE b/c it does not set Product Structure
Chris A. Mattmann created OODT-954: -- Summary: CAS-PGE FileManagerFileStager has NPE b/c it does not set Product Structure Key: OODT-954 URL: https://issues.apache.org/jira/browse/OODT-954 Project: OODT Issue Type: Bug Components: file manager, pge wrapper framework Affects Versions: 1.0 Reporter: Chris A. Mattmann Assignee: Chris A. Mattmann Priority: Blocker Fix For: 1.1 I found this while testing 1.1 RC #1 - the FileManagerFileStager doesn't set the Product.ProductStructure property causing it to be inoperable for use in File Staging. I'll contribute a quick fix and unit test shortly for it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-393) Column Based Catalog for Filemanager
[ https://issues.apache.org/jira/browse/OODT-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-393. Resolution: Won't Fix no time and no big demand > Column Based Catalog for Filemanager > > > Key: OODT-393 > URL: https://issues.apache.org/jira/browse/OODT-393 > Project: OODT > Issue Type: New Feature > Components: file manager >Affects Versions: 0.4 >Reporter: Michael Starch >Assignee: Chris A. Mattmann >Priority: Minor > Fix For: 1.1 > > > This issue is to port the ColumnedBasedCatalog back-end that works with the > JPL filemanager to a place at Apache. > It uses a column-based table structure in the database back-end, which is > more efficient for most databases as it is a true relational structure. This > will also add in the "ComplexQuery" feature that exists in the JPL branch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OODT-808) Replace OODT's XMLPRC with Avro's RPC
[ https://issues.apache.org/jira/browse/OODT-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann reassigned OODT-808: -- Assignee: Chris A. Mattmann (was: Radu Manole) > Replace OODT's XMLPRC with Avro's RPC > - > > Key: OODT-808 > URL: https://issues.apache.org/jira/browse/OODT-808 > Project: OODT > Issue Type: Epic > Components: xmlps >Reporter: Lewis John McGibbney >Assignee: Chris A. Mattmann > Labels: gsoc2015 > Fix For: 1.2 > > Attachments: OODT Avro RPC Project Proposal.docx, OODT Project > Proposal.pdf > > > OODT relies on a legacy [Remote Procedure > Call|http://en.wikipedia.org/wiki/Remote_procedure_call] implementation, > namely [Apache XML-RPC|https://ws.apache.org/xmlrpc/]. Our version of this > library currently sits at 2.0.1, which was released on 28th December 2005. > This issue proposes to replace the convoluted XML-RPC logic with [Apache > Avro's|http://avro.apache.org] [RPC > Protocol|http://avro.apache.org/docs/1.7.7/spec.html#Protocol+Declaration] > implementation. > Right now xmlrpc implementation logic exists in the following OODT modules: > * catalog > * commons > * crawler > * filemgr > * mvn > * pcs > * protocol/api > * pushpull > * resource > * workflow -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OODT-808) Replace OODT's XMLPRC with Avro's RPC
[ https://issues.apache.org/jira/browse/OODT-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated OODT-808: --- Fix Version/s: (was: 1.1) 1.2 > Replace OODT's XMLPRC with Avro's RPC > - > > Key: OODT-808 > URL: https://issues.apache.org/jira/browse/OODT-808 > Project: OODT > Issue Type: Epic > Components: xmlps >Reporter: Lewis John McGibbney >Assignee: Radu Manole > Labels: gsoc2015 > Fix For: 1.2 > > Attachments: OODT Avro RPC Project Proposal.docx, OODT Project > Proposal.pdf > > > OODT relies on a legacy [Remote Procedure > Call|http://en.wikipedia.org/wiki/Remote_procedure_call] implementation, > namely [Apache XML-RPC|https://ws.apache.org/xmlrpc/]. Our version of this > library currently sits at 2.0.1, which was released on 28th December 2005. > This issue proposes to replace the convoluted XML-RPC logic with [Apache > Avro's|http://avro.apache.org] [RPC > Protocol|http://avro.apache.org/docs/1.7.7/spec.html#Protocol+Declaration] > implementation. > Right now xmlrpc implementation logic exists in the following OODT modules: > * catalog > * commons > * crawler > * filemgr > * mvn > * pcs > * protocol/api > * pushpull > * resource > * workflow -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-853) OODT PGE printing of null keys
[ https://issues.apache.org/jira/browse/OODT-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-853. Resolution: Won't Fix nice to have, but haven't got around to this > OODT PGE printing of null keys > -- > > Key: OODT-853 > URL: https://issues.apache.org/jira/browse/OODT-853 > Project: OODT > Issue Type: Improvement >Affects Versions: 0.9 >Reporter: Andrea DeMarco >Assignee: Chris A. Mattmann >Priority: Minor > Fix For: 1.1 > > > Can I suggest that the OODT PGE prints out what keys are actually null before > throwing an exception - this would make it easier to debug. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OODT-869) Integrate Avro RPC with the commons module
[ https://issues.apache.org/jira/browse/OODT-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated OODT-869: --- Fix Version/s: (was: 1.1) 1.2 > Integrate Avro RPC with the commons module > -- > > Key: OODT-869 > URL: https://issues.apache.org/jira/browse/OODT-869 > Project: OODT > Issue Type: Sub-task > Components: commons >Reporter: Radu Manole >Assignee: Chris A. Mattmann > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OODT-868) Integrate Avro RPC with the pcs module
[ https://issues.apache.org/jira/browse/OODT-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann reassigned OODT-868: -- Assignee: Chris A. Mattmann (was: Radu Manole) > Integrate Avro RPC with the pcs module > -- > > Key: OODT-868 > URL: https://issues.apache.org/jira/browse/OODT-868 > Project: OODT > Issue Type: Sub-task > Components: pcs >Reporter: Radu Manole >Assignee: Chris A. Mattmann > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OODT-867) Integrate Avro RPC with the resource module
[ https://issues.apache.org/jira/browse/OODT-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann reassigned OODT-867: -- Assignee: Chris A. Mattmann (was: Radu Manole) > Integrate Avro RPC with the resource module > --- > > Key: OODT-867 > URL: https://issues.apache.org/jira/browse/OODT-867 > Project: OODT > Issue Type: Sub-task > Components: resource manager >Reporter: Radu Manole >Assignee: Chris A. Mattmann > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (OODT-869) Integrate Avro RPC with the commons module
[ https://issues.apache.org/jira/browse/OODT-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann reassigned OODT-869: -- Assignee: Chris A. Mattmann (was: Radu Manole) > Integrate Avro RPC with the commons module > -- > > Key: OODT-869 > URL: https://issues.apache.org/jira/browse/OODT-869 > Project: OODT > Issue Type: Sub-task > Components: commons >Reporter: Radu Manole >Assignee: Chris A. Mattmann > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OODT-867) Integrate Avro RPC with the resource module
[ https://issues.apache.org/jira/browse/OODT-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated OODT-867: --- Fix Version/s: (was: 1.1) 1.2 > Integrate Avro RPC with the resource module > --- > > Key: OODT-867 > URL: https://issues.apache.org/jira/browse/OODT-867 > Project: OODT > Issue Type: Sub-task > Components: resource manager >Reporter: Radu Manole >Assignee: Radu Manole > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OODT-868) Integrate Avro RPC with the pcs module
[ https://issues.apache.org/jira/browse/OODT-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated OODT-868: --- Fix Version/s: (was: 1.1) 1.2 > Integrate Avro RPC with the pcs module > -- > > Key: OODT-868 > URL: https://issues.apache.org/jira/browse/OODT-868 > Project: OODT > Issue Type: Sub-task > Components: pcs >Reporter: Radu Manole >Assignee: Chris A. Mattmann > Fix For: 1.2 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-857) Use custom Avro data types in the Catalog module
[ https://issues.apache.org/jira/browse/OODT-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-857. Resolution: Won't Fix catalog module is gone > Use custom Avro data types in the Catalog module > > > Key: OODT-857 > URL: https://issues.apache.org/jira/browse/OODT-857 > Project: OODT > Issue Type: Sub-task > Components: catalog >Reporter: Radu Manole >Assignee: Radu Manole > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-709) Add documentation to Wiki describing how one can add new Maven profile configurations
[ https://issues.apache.org/jira/browse/OODT-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-709. Resolution: Fixed > Add documentation to Wiki describing how one can add new Maven profile > configurations > - > > Key: OODT-709 > URL: https://issues.apache.org/jira/browse/OODT-709 > Project: OODT > Issue Type: Sub-task > Components: radix >Affects Versions: 0.6 >Reporter: Rishi Verma >Assignee: Rishi Verma > Fix For: 1.1 > > > Add documentation to Wiki describing how one can add new Maven profile > configurations. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-773) pushpull script parameters should not be resolved locally
[ https://issues.apache.org/jira/browse/OODT-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-773. Resolution: Won't Fix there is no more push pull > pushpull script parameters should not be resolved locally > - > > Key: OODT-773 > URL: https://issues.apache.org/jira/browse/OODT-773 > Project: OODT > Issue Type: Improvement > Components: push pull framework >Affects Versions: 0.7 >Reporter: Lewis John McGibbney >Assignee: Lewis John McGibbney > Fix For: 1.1 > > Attachments: OODT-773.patch > > > This issue was raised a while ago by (0) [~angela_wang] but AFAIK it was not > logged. > Essentially it has to do with some paths being qualified and some existing as > local to the directory in which you run the pushpull script. The solution is > for us to ensure that all paths are qualified and can be resolved regardless > of where the script is run from. > (0) http://www.mail-archive.com/dev%40oodt.apache.org/msg04257.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-626) Unit tests for TestDeleteProductByName and TestDeleteProductById don't override all needed methods in getClient
[
https://issues.apache.org/jira/browse/OODT-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-626.
Resolution: Fixed
apparently this is fixed now. No clue why
> Unit tests for TestDeleteProductByName and TestDeleteProductById don't
> override all needed methods in getClient
> ---
>
> Key: OODT-626
> URL: https://issues.apache.org/jira/browse/OODT-626
> Project: OODT
> Issue Type: Bug
> Components: file manager
> Environment: Mac OS X 10.8.3
> [chipotle:oodt/trunk/filemgr] mattmann% java -version
> java version "1.6.0_45"
> Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406)
> Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode)
> [chipotle:oodt/trunk/filemgr] mattmann%
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
> Fix For: 1.1
>
>
> While investigating a possible policy bug, I ran into the issue with the
> following two hanging action tests:
> * TestDeleteProductByIdAction
> * TestDeleteProductByNameAction
> Take the first action test, TestDeleteProductByIdAction. While investigating,
> I found that it hangs in this method on line 75 where it is creating a mock
> object FalseDeleteProductByNameCliAction.
> {code:java}
> cliAction = new FalseDeleteProductByNameCliAction();
> cliAction.setProductName(PRODUCT_NAME);
> try {
> cliAction.execute(printer);
> fail("Expected throw CmdLineActionException");
> } catch (CmdLineActionException ignore) {
> }
> {code}
> The actual line it hangs in is in cliAction.execute. Looking in that line it
> seems to hang because in AbstractDeleteProductionAction, line 50, due to this
> code block:
> {code:java}
> for (Reference ref : refs) {
> if (!client.removeFile(new File(new
> URI(ref.getDataStoreReference()))
> .getAbsolutePath())) {
>throw new Exception("Failed to delete file '"
> + ref.getDataStoreReference() + "'");
> }
> }
> {code}
> Basically it seems that TestGetDeleteProductByIdAction and its subclass
> FalseDeleteProductByNameCliAction do not define the method, removeFile, which
> in turn is called by the above code. The only problem is that version of that
> function that is called is the XmlRpcFileManagerClient#removeFile, which
> actually tries to make an XmlRpc connection. Because of the code here:
> {code:java}
> CommonsXmlRpcTransport transport = new CommonsXmlRpcTransport(
> url, client);
> transport
> .setConnectionTimeout(Integer
> .getInteger(
>
> "org.apache.oodt.cas.filemgr.system.xmlrpc.connectionTimeout.minutes",
> 20).intValue() * 60 * 1000);
> transport
> .setTimeout(Integer
> .getInteger(
>
> "org.apache.oodt.cas.filemgr.system.xmlrpc.requestTimeout.minutes",
> 60).intValue() * 60 * 1000);
> {code}
> it seems like this test should hang forever, and time out (or at least for 60
> minutes). However, we don't notice this...on tests that run on our own
> Jenkins server:
> https://builds.apache.org/job/oodt-trunk/964/org.apache.oodt$cas-filemgr/console
> Or on some of our dev computers (e.g., Andrew Hart's ubtuntu VM).
> Also I don't remember this failing over the past year too much and this code
> has existed for well over this time. So, I'm stumped. In the interest of
> helping anyone else that has this problem I attach a patch that fixes these 2
> tests by adding local override implementations of the methods removeFile and
> others required to intercept the calls and to stay away from XML-RPC calls.
> Brian Foster or anyone else it would be great if you can comment here.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (OODT-491) Finish line tasks for Wengine integration
[ https://issues.apache.org/jira/browse/OODT-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated OODT-491: --- Fix Version/s: (was: 1.1) 1.2 > Finish line tasks for Wengine integration > - > > Key: OODT-491 > URL: https://issues.apache.org/jira/browse/OODT-491 > Project: OODT > Issue Type: Umbrella > Components: workflow manager >Reporter: Chris A. Mattmann >Assignee: Chris A. Mattmann > Fix For: 1.2 > > Attachments: NewWorkflowModel.patch.txt > > > The final tasks to wrap up wengine integration into trunk. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-565) Fix XMLPS CDEResult and CDEInputStream unit tests to use orderedFIelds
[ https://issues.apache.org/jira/browse/OODT-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-565. Resolution: Won't Fix no time > Fix XMLPS CDEResult and CDEInputStream unit tests to use orderedFIelds > -- > > Key: OODT-565 > URL: https://issues.apache.org/jira/browse/OODT-565 > Project: OODT > Issue Type: Bug > Components: xmlps >Reporter: Chris A. Mattmann >Assignee: Chris A. Mattmann > Fix For: 1.1 > > > In keeping back compat in OODT-564, I didn't modify the unit tests for > CDEResult or CDEResultInputStream, and instead worked around by keeping the > old behavior for serializing the output of the XMLPS product server using > only the rs#getResultSetMetadata if orderedFields aren't set (like they > aren't in the unit tests). But this is a hack, b/c we expect orderedFields to > now be set (should probably throw an Exception somewhere if they are not > rather than failing silently until it gives the wrong results). > So, fix the unit tests to explicitly test and require this. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (OODT-519) Fix calculation and computation of Wall Clock Time for Task and Workflow Level, and Current Task
[ https://issues.apache.org/jira/browse/OODT-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated OODT-519: --- Fix Version/s: (was: 1.1) 1.2 > Fix calculation and computation of Wall Clock Time for Task and Workflow > Level, and Current Task > > > Key: OODT-519 > URL: https://issues.apache.org/jira/browse/OODT-519 > Project: OODT > Issue Type: Sub-task > Components: workflow manager >Reporter: Chris A. Mattmann >Assignee: Chris A. Mattmann > Fix For: 1.2 > > > Currently there is a bug in the computation of wall clock time for tasks and > workflows, and the current task isn't being calculated correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-158) QuerySets for XMLPS
[
https://issues.apache.org/jira/browse/OODT-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-158.
Resolution: Won't Fix
no time
> QuerySets for XMLPS
> ---
>
> Key: OODT-158
> URL: https://issues.apache.org/jira/browse/OODT-158
> Project: OODT
> Issue Type: Improvement
> Components: xmlps
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
> Labels: bakedin, query, queryset, xmlps
> Fix For: 1.1
>
>
> [~davekale] and I have been discussing the notion of "query sets" for XMLPS.
> These would turn long, huge queryStrings for XMLPS, e.g.,:
> {noformat}
> http://host:8080/grid/prod?q=RETURN=ID%20AND%20RETURN=UnitNumber%20AND%20RETURN=AcctNum%20AND%20RETURN=HospitalAdmitDate%20AND%20RETURN=AdmitDateTime%20AND%20RETURN=AdmitDate%20AND%20RETURN=AdmitTime%20AND%20RETURN=Service%20AND%20RETURN=AdmitCategory%20AND%20RETURN=ZipCode%20AND%20RETURN=ZipRegion%20AND%20RETURN=Origin%20AND%20RETURN=ReferringHospital%20AND%20RETURN=Doctor%20AND%20RETURN=ReferringService%20AND%20RETURN=DischargeCondition%20AND%20RETURN=Disposition%20AND%20RETURN=Payment%20AND%20RETURN=PICULocation%20AND%20RETURN=DischargeDateTime%20AND%20RETURN=DischargeDate%20AND%20RETURN=DischargeTime%20AND%20RETURN=Planned%20AND%20RETURN=PRISM%20AND%20RETURN=MortProb%20AND%20RETURN=OperativeType%20AND%20RETURN=isScheduled%20AND%20RETURN=isTrauma%20AND%20RETURN=FEStudy%20AND%20RETURN=Weight%20AND%20RETURN=Height%20AND%20RETURN=HeadCircumference%20AND%20RETURN=AdmitPCPC%20AND%20RETURN=DischargePCPC%20AND%20RETURN=AdmitPOPC%20AND%20RETURN=DischargePOPC%20AND%20RETURN=ToDoList%20AND%20RETURN=Bed%20AND%20RETURN=Resident%20AND%20RETURN=isVerified%20AND%20RETURN=VerifiedBy%20AND%20RETURN=OrganDonor%20AND%20RETURN=OrganProcurementNotified%20AND%20RETURN=DeathReason%20AND%20RETURN=DischargeNote%20AND%20RETURN=OriginText%20AND%20RETURN=DispositionText%20AND%20RETURN=DeathNote%20AND%20RETURN=DeathFellow%20AND%20RETURN=DeathAttending%20AND%20RETURN=HospDCDate%20AND%20RETURN=HospDCStatus%20AND%20RETURN=ADT%20AND%20RETURN=BillingSameIllness%20AND%20RETURN=BillingSameIllnessDate%20AND%20RETURN=BillingAccident%20AND%20RETURN=BillingAccidentType%20AND%20RETURN=BillingEmergentService%20AND%20RETURN=BillingSimilarIllness%20AND%20RETURN=BillingSimilarIllnessDate%20AND%20RETURN=BillingAccidentDate%20AND%20RETURN=upsize_ts%20AND%20RETURN=FirstVital%20AND%20RETURN=LastVital%20AND%20RETURN=influenza_like_illness
> {noformat}
> into something like:
> {noformat}
> http://host:8080/grid/prod?q=RETURN%3DPICUDBQSET
> {noformat}
> which would then require some configuration say in XMLPS, something like:
> {code:xml}
>
> ...
>
>
>
> ...
>
>
> {code}
> In other words, we're talking about baked-in, canned queries for XMLPS prod
> servers that are mainly used for dumping.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OODT-204) WorkflowTaskConfig should save envReplace switch information
[ https://issues.apache.org/jira/browse/OODT-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-204. Resolution: Fixed the basics of this are here in the new policy package in workflow > WorkflowTaskConfig should save envReplace switch information > > > Key: OODT-204 > URL: https://issues.apache.org/jira/browse/OODT-204 > Project: OODT > Issue Type: Improvement > Components: workflow manager > Environment: From JPL's last internal WM release >Reporter: Chris A. Mattmann >Assignee: Chris A. Mattmann > Fix For: 1.1 > > > Currently the WorkflowTaskConfiguration doesn't save whether or not a a task > config property was envReplaced or not: it should store this information so > that we know, e.g., in a TaskPolicyWriter, whether a property was envReplaced > so that the information can be properly rewritten out. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-916) remove magic numbers
[ https://issues.apache.org/jira/browse/OODT-916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-916. Resolution: Won't Fix hi [~krishnarb3] I think this is another example where we need much more specificity. Open a new issue if there is something specific to fix. > remove magic numbers > > > Key: OODT-916 > URL: https://issues.apache.org/jira/browse/OODT-916 > Project: OODT > Issue Type: Bug >Reporter: Tom Barber >Priority: Trivial > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-512) Allow Injection of Metadata into SolrIndexer from Config
[ https://issues.apache.org/jira/browse/OODT-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-512. Resolution: Won't Fix nice to have > Allow Injection of Metadata into SolrIndexer from Config > > > Key: OODT-512 > URL: https://issues.apache.org/jira/browse/OODT-512 > Project: OODT > Issue Type: Improvement > Components: file manager >Affects Versions: 0.4 >Reporter: Paul Ramirez >Assignee: Paul Ramirez >Priority: Trivial > Fix For: 1.1 > > > This will simplify the code and generalize the approach used for injecting > things such as ProductURL. > The idea is to simply allow for: > met.ProductURL=http://localhost:8080/cas-product?productID=[CAS.ProductId] > Multivalued metadata could be injected by just using a comma separated list. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-917) replace hashtable with hashmap
[ https://issues.apache.org/jira/browse/OODT-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-917. Resolution: Won't Fix Hi [~krishnarb3] if you have interest in working on this issue please submit a new issue/PR with something specific since this one is too broad. Please only open that issue when you actually have a fix in mind. Thank you! > replace hashtable with hashmap > -- > > Key: OODT-917 > URL: https://issues.apache.org/jira/browse/OODT-917 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > > Hashtable is part of the obsolete dictionary class and whilst threadsafe is > slower and more memory intesive than a hashmap, if threadsafety is required > Hashmap can provide the concurrenthashmap -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-513) Provide Documentation for SolrIndexer Config
[ https://issues.apache.org/jira/browse/OODT-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-513. Resolution: Won't Fix nice to have > Provide Documentation for SolrIndexer Config > > > Key: OODT-513 > URL: https://issues.apache.org/jira/browse/OODT-513 > Project: OODT > Issue Type: Improvement > Components: file manager >Affects Versions: 0.4 >Reporter: Paul Ramirez >Assignee: Paul Ramirez >Priority: Trivial > Fix For: 1.1 > > > How the property file works is a bit mysterious and can easily be documented > directly in the file. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-908) replace system.out.println with log calls
[ https://issues.apache.org/jira/browse/OODT-908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-908. Resolution: Won't Fix great idea if there was time > replace system.out.println with log calls > - > > Key: OODT-908 > URL: https://issues.apache.org/jira/browse/OODT-908 > Project: OODT > Issue Type: Bug >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-903) code quality - simplify flows
[ https://issues.apache.org/jira/browse/OODT-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-903. Resolution: Won't Fix which ones > code quality - simplify flows > - > > Key: OODT-903 > URL: https://issues.apache.org/jira/browse/OODT-903 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Assignee: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-907) code quality - remove never queried collections
[ https://issues.apache.org/jira/browse/OODT-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-907. Resolution: Won't Fix good idea, no time > code quality - remove never queried collections > --- > > Key: OODT-907 > URL: https://issues.apache.org/jira/browse/OODT-907 > Project: OODT > Issue Type: Bug >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-904) remove redundant throws
[ https://issues.apache.org/jira/browse/OODT-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-904. Resolution: Won't Fix throwing this out > remove redundant throws > --- > > Key: OODT-904 > URL: https://issues.apache.org/jira/browse/OODT-904 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > > Lots of methods have old throw clauses that are never used and should be > removed -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-902) remove redundant modifiers from enums
[ https://issues.apache.org/jira/browse/OODT-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-902. Resolution: Won't Fix need much more detail > remove redundant modifiers from enums > - > > Key: OODT-902 > URL: https://issues.apache.org/jira/browse/OODT-902 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Assignee: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-901) resolve some javadoc issues
[ https://issues.apache.org/jira/browse/OODT-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-901. Resolution: Won't Fix which ones > resolve some javadoc issues > --- > > Key: OODT-901 > URL: https://issues.apache.org/jira/browse/OODT-901 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-906) remove redundant assignment
[ https://issues.apache.org/jira/browse/OODT-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-906. Resolution: Won't Fix which ones > remove redundant assignment > --- > > Key: OODT-906 > URL: https://issues.apache.org/jira/browse/OODT-906 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Assignee: Tom Barber >Priority: Minor > Fix For: 1.1 > > > there are lots of varx = null; and similar which aren't required and add > unneeded clutter. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-897) code quality - unnecessary module dependency
[ https://issues.apache.org/jira/browse/OODT-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-897. Resolution: Won't Fix not enough detail > code quality - unnecessary module dependency > > > Key: OODT-897 > URL: https://issues.apache.org/jira/browse/OODT-897 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-896) code quality - unnecessary interface modifier
[ https://issues.apache.org/jira/browse/OODT-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-896. Resolution: Won't Fix nice to have > code quality - unnecessary interface modifier > - > > Key: OODT-896 > URL: https://issues.apache.org/jira/browse/OODT-896 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-900) code-quality remove unneeded boxing, unboxing, swap indexof to contains, stringbuffer to builder
[ https://issues.apache.org/jira/browse/OODT-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-900. Resolution: Won't Fix good idea, no time > code-quality remove unneeded boxing, unboxing, swap indexof to contains, > stringbuffer to builder > > > Key: OODT-900 > URL: https://issues.apache.org/jira/browse/OODT-900 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-899) code quality - redundant local variable
[ https://issues.apache.org/jira/browse/OODT-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-899. Resolution: Won't Fix which one? > code quality - redundant local variable > --- > > Key: OODT-899 > URL: https://issues.apache.org/jira/browse/OODT-899 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-898) code quality - remove redundant private final call
[ https://issues.apache.org/jira/browse/OODT-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-898. Resolution: Won't Fix no time > code quality - remove redundant private final call > -- > > Key: OODT-898 > URL: https://issues.apache.org/jira/browse/OODT-898 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-895) code quality - redundant measure unit
[ https://issues.apache.org/jira/browse/OODT-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-895. Resolution: Won't Fix no clue what this is > code quality - redundant measure unit > - > > Key: OODT-895 > URL: https://issues.apache.org/jira/browse/OODT-895 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-888) Replace appended string with StringBuilder to improve performance
[ https://issues.apache.org/jira/browse/OODT-888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-888. Resolution: Won't Fix great idea, no time > Replace appended string with StringBuilder to improve performance > - > > Key: OODT-888 > URL: https://issues.apache.org/jira/browse/OODT-888 > Project: OODT > Issue Type: Bug >Reporter: Tom Barber >Assignee: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-894) Tidy up inefficient constructors (sonar)
[ https://issues.apache.org/jira/browse/OODT-894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-894. Resolution: Won't Fix another nice to have if there was time > Tidy up inefficient constructors (sonar) > > > Key: OODT-894 > URL: https://issues.apache.org/jira/browse/OODT-894 > Project: OODT > Issue Type: Improvement >Reporter: Tom Barber >Assignee: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-859) Convert Jars to OSGI Bundles
[ https://issues.apache.org/jira/browse/OODT-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-859. Resolution: Incomplete We've got a branch this isn't done yet, but if there is interest, work on the branch. > Convert Jars to OSGI Bundles > > > Key: OODT-859 > URL: https://issues.apache.org/jira/browse/OODT-859 > Project: OODT > Issue Type: Bug >Reporter: Tom Barber >Assignee: Tom Barber >Priority: Minor > Fix For: 1.1 > > > For various reasons we should include the OSGI compliant MANIFEST headers. > The poms need updating to build it that is all. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-760) Allow for pushpull fileretriction parsers to support metadata parsing
[ https://issues.apache.org/jira/browse/OODT-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-760. Resolution: Won't Fix no push pull > Allow for pushpull fileretriction parsers to support metadata parsing > - > > Key: OODT-760 > URL: https://issues.apache.org/jira/browse/OODT-760 > Project: OODT > Issue Type: Bug > Components: push pull framework >Affects Versions: 0.7 > Environment: none >Reporter: Brian Foster >Assignee: Brian Foster >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-743) Check OODT date time utility classes and work out what can be removed/optimised
[ https://issues.apache.org/jira/browse/OODT-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-743. Resolution: Won't Fix good idea, but no time > Check OODT date time utility classes and work out what can be > removed/optimised > --- > > Key: OODT-743 > URL: https://issues.apache.org/jira/browse/OODT-743 > Project: OODT > Issue Type: Improvement > Components: commons >Reporter: Tom Barber >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-683) Create deleteOnSuccess option for pushpull config files
[ https://issues.apache.org/jira/browse/OODT-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-683. Resolution: Won't Fix no more push pull > Create deleteOnSuccess option for pushpull config files > --- > > Key: OODT-683 > URL: https://issues.apache.org/jira/browse/OODT-683 > Project: OODT > Issue Type: Bug > Components: push pull framework >Affects Versions: 0.7 > Environment: none >Reporter: Brian Foster >Assignee: Brian Foster >Priority: Minor > Fix For: 1.1 > > > For cases where the config files for downloading other files is emails, you > typically just want to delete the successful once so they don't clutter up > space -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-766) NullPointerException occurs when no result returned from the query_tool script
[ https://issues.apache.org/jira/browse/OODT-766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-766. Resolution: Won't Fix work around - expected behavior > NullPointerException occurs when no result returned from the query_tool script > -- > > Key: OODT-766 > URL: https://issues.apache.org/jira/browse/OODT-766 > Project: OODT > Issue Type: Bug > Components: file manager >Affects Versions: 0.6 > Environment: Mac OS.X 10.9.2 >Reporter: Mengying Wang >Priority: Minor > Fix For: 1.1 > > > Following the tutorial > http://oodt.apache.org/components/maven/curator/user/basic.html, I added a > new JSON product type to my file manager. However, if I run the query_tool > script before any json files ingested, it will raise some errors, as shown > here: > $ ./query_tool --url http://localhost:9000 --sql -query "SELECT * FROM JSON" > Oct 27, 2014 11:52:07 PM org.apache.oodt.cas.filemgr.catalog.LuceneCatalog > paginateQuery > WARNING: Query: [q=] for Product Type: [urn:example:JSON] returned no > results > java.lang.NullPointerException > at > org.apache.oodt.cas.filemgr.system.XmlRpcFileManager.complexQuery(XmlRpcFileManager.java:602) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.xmlrpc.Invoker.execute(Invoker.java:130) > at org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84) > at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146) > at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139) > at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125) > at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761) > at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642) > at java.lang.Thread.run(Thread.java:744) > org.apache.xmlrpc.XmlRpcException: java.lang.Exception: > org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed to > perform complex query : null > at > org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:104) > at > org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:71) > at org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73) > at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194) > at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185) > at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178) > at > org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:990) > at > org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.java:252) > at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242) > Exception in thread "main" > org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: > java.lang.Exception: > org.apache.oodt.cas.filemgr.structs.exceptions.CatalogException: Failed to > perform complex query : null > at > org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.complexQuery(XmlRpcFileManagerClient.java:996) > at > org.apache.oodt.cas.filemgr.tools.QueryTool.performSqlQuery(QueryTool.java:252) > at org.apache.oodt.cas.filemgr.tools.QueryTool.main(QueryTool.java:242) > By the way, if some files with the product type JSON are already ingested > in my file manager, then the query_tool script works very well. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-730) Add Protocol CLI action for deleting empty directories from sites
[ https://issues.apache.org/jira/browse/OODT-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-730. Resolution: Won't Fix no push pull anymore > Add Protocol CLI action for deleting empty directories from sites > - > > Key: OODT-730 > URL: https://issues.apache.org/jira/browse/OODT-730 > Project: OODT > Issue Type: Bug > Components: push pull framework > Environment: none >Reporter: Brian Foster >Assignee: Brian Foster >Priority: Minor > Fix For: 1.1 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-714) Make OODT RADiX vagrant boxes available on vagrantcloud.com
[ https://issues.apache.org/jira/browse/OODT-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-714. Resolution: Won't Fix not enough interest > Make OODT RADiX vagrant boxes available on vagrantcloud.com > --- > > Key: OODT-714 > URL: https://issues.apache.org/jira/browse/OODT-714 > Project: OODT > Issue Type: Task > Components: radix >Reporter: Sheryl John >Assignee: Sheryl John >Priority: Minor > Fix For: 1.1 > > > [Vagrant Cloud|https://vagrantcloud.com] holds available vagrant boxes to > start off a VM. > With Rishi's vagrant box setup for OODT RADiX [OODT-676], the created boxes > can be added and released to Vagrant via vagrantcloud. > Additional info : https://vagrantcloud.com/help -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-702) Add Encryption support to S3 DataTransferer
[ https://issues.apache.org/jira/browse/OODT-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-702. Resolution: Won't Fix no time I guess > Add Encryption support to S3 DataTransferer > --- > > Key: OODT-702 > URL: https://issues.apache.org/jira/browse/OODT-702 > Project: OODT > Issue Type: Bug > Components: file manager >Affects Versions: 0.7 > Environment: none >Reporter: Brian Foster >Assignee: Brian Foster >Priority: Minor > Fix For: 1.1 > > > Need to support encryption in the S3 Data Transferer within CAS-File Managr. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-682) Filemgr behaves differently when clientTransfer is enabled
[ https://issues.apache.org/jira/browse/OODT-682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-682. Resolution: Won't Fix would be a great issue, but no time to fix > Filemgr behaves differently when clientTransfer is enabled > -- > > Key: OODT-682 > URL: https://issues.apache.org/jira/browse/OODT-682 > Project: OODT > Issue Type: Improvement > Components: file manager >Affects Versions: 0.7 > Environment: none >Reporter: Brian Foster >Assignee: Brian Foster >Priority: Minor > Fix For: 1.1 > > > Because the MetExtractors always run server-side, when client-side versioning > happens the MetExtractor generated metadata is not available for the > Versioner (this works find when server-side versioning is used). > - this fix will sync product metadata to client before running versioning > when clientTransfer is enabled. > Probably best long-term fix for this is to move MetExtraction to client-side > as well when clientTransfer is enabled... but making that clean and factoring > out the code correctly is a bigger task... will put fix mentioned above in > for now and later work on maybe this approach as a final fix. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-684) Multi-Threaded ingests for Crawler
[ https://issues.apache.org/jira/browse/OODT-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-684. Resolution: Won't Fix great idea, no time > Multi-Threaded ingests for Crawler > -- > > Key: OODT-684 > URL: https://issues.apache.org/jira/browse/OODT-684 > Project: OODT > Issue Type: Bug > Components: crawler >Affects Versions: 0.7 > Environment: none >Reporter: Brian Foster >Assignee: Brian Foster >Priority: Minor > Fix For: 1.1 > > > This will be available for all Crawlers... it will be turned on via a flag... > this will allow for a priority based worker pool can be plugged in at a later > date which could even be used to prioritize which product type get ingested > first. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-581) Update and upgrade usage of Lucene core dependency to write File Manager catalogs
[ https://issues.apache.org/jira/browse/OODT-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-581. Resolution: Won't Fix since we moved to dependency Management it will be nearly impossible to get this current patch working and without a big call for getting this done I don't have the time to invest here. Thanks for the hard work regardless Lewis. > Update and upgrade usage of Lucene core dependency to write File Manager > catalogs > -- > > Key: OODT-581 > URL: https://issues.apache.org/jira/browse/OODT-581 > Project: OODT > Issue Type: Improvement > Components: catalog, file manager >Reporter: Lewis John McGibbney >Assignee: Chris A. Mattmann >Priority: Minor > Fix For: 1.1 > > Attachments: OODT-581-notes.txt, OODT-581.patch, OODT-581.patch > > > As recently explained on the user@ list [0], FM could so with an upgrade of > the lucene-core library for improved writing of catalogs. > We can discuss which new features we can leverage from lucene-core 4.X > [0] http://www.mail-archive.com/user%40oodt.apache.org/msg00603.html -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-671) Ensure OODT trunk builds and tests successfully on Windows OS
[ https://issues.apache.org/jira/browse/OODT-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-671. Resolution: Fixed the one sub-task this had is fixed. So it's fixed. > Ensure OODT trunk builds and tests successfully on Windows OS > - > > Key: OODT-671 > URL: https://issues.apache.org/jira/browse/OODT-671 > Project: OODT > Issue Type: Bug > Components: build proces >Affects Versions: 0.6 > Environment: Windows OS (all) >Reporter: Lewis John McGibbney >Assignee: Lewis John McGibbney >Priority: Minor > Labels: gsoc, newbie > Fix For: 1.1 > > > We recently got a Windows CI build up and running > https://builds.apache.org/job/oodt-trunk-Windows/ > We need to ensure that all code and tests are Windows OS compatible. > This issue should track the fix. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-680) Filemgr should delete files using DataTransferer
[ https://issues.apache.org/jira/browse/OODT-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-680. Resolution: Won't Fix not sure how/what/why to fix this and what needs fixing. > Filemgr should delete files using DataTransferer > > > Key: OODT-680 > URL: https://issues.apache.org/jira/browse/OODT-680 > Project: OODT > Issue Type: Improvement > Components: file manager >Affects Versions: 0.7 > Environment: none >Reporter: Brian Foster >Assignee: Brian Foster >Priority: Minor > Fix For: 1.1 > > > currently removeFile(String path) just does new File(path).delete()... this > doesn't work for other datatransferers like S3. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-567) show JAVA_HOME env var in RADiX start command in all cases
[
https://issues.apache.org/jira/browse/OODT-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-567.
Resolution: Won't Fix
nice to have, but no time
> show JAVA_HOME env var in RADiX start command in all cases
> --
>
> Key: OODT-567
> URL: https://issues.apache.org/jira/browse/OODT-567
> Project: OODT
> Issue Type: Bug
> Components: radix
>Affects Versions: 0.5
>Reporter: Andrew Hart
>Assignee: Andrew Hart
>Priority: Minor
> Fix For: 1.1
>
>
> The RADiX deployment script prints out a list of the environment variables
> when it starts up. This looks something like:
> {code}
> user@foo ~/Development/sandbox/oodt-deploy/bin $ ./oodt start
> Using OODT_BASE: /home/user/Development/sandbox/oodt-deploy
> Using OODT_HOME: /home/user/Development/sandbox/oodt-deploy
> Using OODT_TMPDIR: /home/user/Development/sandbox/oodt-deploy/temp
> Using JRE_HOME:/usr
> Using CLASSPATH:
> {code}
> A common startup problem is related to JAVA_HOME not being properly set on
> the target system. Currently, the RADiX script only includes the JAVA_HOME
> value if the the "oodt" command is run with the debug flag. To make it easier
> to immediately diagnose potential environment problems, the value for
> JAVA_HOME should be displayed in all modes of operation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OODT-539) New maven archetype for generating a template MetExtractor project
[ https://issues.apache.org/jira/browse/OODT-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-539. Resolution: Won't Fix a great idea, but no one has done this since end of 2012 - not going to get done, unfortunately > New maven archetype for generating a template MetExtractor project > -- > > Key: OODT-539 > URL: https://issues.apache.org/jira/browse/OODT-539 > Project: OODT > Issue Type: New Feature > Components: cas-mvn-plugins >Affects Versions: 0.4 >Reporter: Rishi Verma >Assignee: Rishi Verma >Priority: Minor > Fix For: 1.1 > > > Create a new maven archetype for allowing developers to quickly generate > MetExtractor projects on their own. > The rationale for creating this archetype is to make it simpler and quicker > to write new met extractors. Writing new met extractors is pretty easy, but > establishing the correct maven directory structure, pom file(s), and build > cycle can be tricky. I myself often just replicate the directory structure > and pom files from other projects instead of creating/writing new met > extractor projects from scratch. This can however lead to human errors and > also unwanted code and config. Having an archetype which generates a > preferred met extractor-specific maven directory structure, pom files, and > template met extractor code would make the job of creating new custom met > extractors more consistent and automatic. > The proposed capability is the following: > 1. New archetype to generate a full maven project for writing custom met > extractor(s) > 2. Pre-populate generated project with template MetExtractor(s) which work > out-of-the box and make it obvious WHERE developer should add their custom > extraction code > 3. Ensure generated project pom allows a build of met extractor project out > of the box > To start out, I would recommend we include an extended CmdLineMetExtractor > class which works out-of-the box. We can include more custom met extractors > and template code later. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-559) Unit test failure in testDoDynamicReplacement for "Europe/London" timezone
[ https://issues.apache.org/jira/browse/OODT-559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-559. Resolution: Fixed > Unit test failure in testDoDynamicReplacement for "Europe/London" timezone > -- > > Key: OODT-559 > URL: https://issues.apache.org/jira/browse/OODT-559 > Project: OODT > Issue Type: Bug > Components: commons >Affects Versions: 0.6 >Reporter: Varun Ratnakar >Assignee: Chris A. Mattmann >Priority: Minor > Fix For: 1.1 > > Attachments: fix_date_test.patch > > > I've been regularly encountering a unit test failure in > testDoDynamicReplacement. After investigating it a bit further, I found that > it seems to be related to the TimeZone. If I set my computer's timezone to > PST (or any other timezone except "Europe/London"), it works, but with > "Europe/London" Timezone I get the following: > DATE_TO_SECS (2008-01-20T16:30:28.000-33 , TAI_FORMAT , 1993-01-01) > = 474996601.000 > Should be = 475000201.000 > Difference of 3600 seconds = 1 hour -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-536) maven-cas-install plugin cannot handle tarballs with -dist in name.
[ https://issues.apache.org/jira/browse/OODT-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-536. Resolution: Won't Fix known issue - work-around is to rename the distro to be installed. > maven-cas-install plugin cannot handle tarballs with -dist in name. > > > Key: OODT-536 > URL: https://issues.apache.org/jira/browse/OODT-536 > Project: OODT > Issue Type: Bug > Components: cas-mvn-plugins >Reporter: Michael Joyce >Priority: Minor > Fix For: 1.1 > > > Example file name such as "cas-pushpull-0.5-SNAPSHOT-dist.tar.gz" causes "mvn > install" to error out with: > an IO exception occured while untarring the CAS distribution: Message: Source > 'EDRN_ECAS_HOME/cas-pushpull-0.5-SNAPSHOT-dist' does not exist -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-461) GXP support in CAS-PGE
[ https://issues.apache.org/jira/browse/OODT-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-461. Resolution: Won't Fix can achieve same functionality through MetReplaceWriter and also via VelocityTemplateWriter > GXP support in CAS-PGE > -- > > Key: OODT-461 > URL: https://issues.apache.org/jira/browse/OODT-461 > Project: OODT > Issue Type: Improvement > Components: pge wrapper framework >Affects Versions: 0.3 > Environment: none >Reporter: Brian Foster >Assignee: Brian Foster >Priority: Minor > Fix For: 1.1 > > > Support for generation pge configuration files using GXP: > http://code.google.com/p/gxp/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-475) Tool to automatically validate regular expressions in PushPull RemoteSpecs
[
https://issues.apache.org/jira/browse/OODT-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-475.
Resolution: Won't Fix
push pull not part of OODT anymore
> Tool to automatically validate regular expressions in PushPull RemoteSpecs
> --
>
> Key: OODT-475
> URL: https://issues.apache.org/jira/browse/OODT-475
> Project: OODT
> Issue Type: New Feature
> Components: push pull framework
>Reporter: Chris A. Mattmann
>Assignee: Chris A. Mattmann
>Priority: Minor
> Fix For: 1.1
>
>
> While discussing: http://s.apache.org/ff
> I had the idea to create a tool that would simply wrap
> o.a.oodt.cas.pushpull.util.ExpressionValidator and run that command on all
> the regular expressions in a PushPull RemoteSpecs directory. So we could then
> have a bash or tcsh script that wraps that to the effect of:
> {noformat}
> ./validate_remotespecs /path/to/remotespecs/dir
> {noformat}
> Which would then run, and print out line by line:
> [regex string]: valid | not valid
> If it's not valid, you also get the error message.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OODT-479) Add getHost() method to Protocol API Interface
[ https://issues.apache.org/jira/browse/OODT-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-479. Resolution: Won't Fix PushPull isn't part of OODT anymore > Add getHost() method to Protocol API Interface > -- > > Key: OODT-479 > URL: https://issues.apache.org/jira/browse/OODT-479 > Project: OODT > Issue Type: Bug > Components: push pull framework >Affects Versions: 0.4 > Environment: none >Reporter: Brian Foster >Assignee: Brian Foster >Priority: Minor > Fix For: 1.1 > > > Will add the following method to Protocol interface: > public String getHost(); -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-524) Make Curator Task List Persist Across Restarts
[ https://issues.apache.org/jira/browse/OODT-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-524. Resolution: Fixed Assignee: Chris A. Mattmann Done! Thanks Mike! > Make Curator Task List Persist Across Restarts > -- > > Key: OODT-524 > URL: https://issues.apache.org/jira/browse/OODT-524 > Project: OODT > Issue Type: Improvement > Components: curator >Reporter: Michael Joyce >Assignee: Chris A. Mattmann >Priority: Minor > Fix For: 1.1 > > > Currently the curator's task list doesn't persist across restarts. > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-526) Add base functionality in Curator for Task List persistence
[
https://issues.apache.org/jira/browse/OODT-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-526.
Resolution: Fixed
Thanks committed this with minor modifications thanks Mike!
{noformat}
LMC-053601:oodt mattmann$ git commit -m "Fix for OODT-526: Add base
functionality in Curator for Task List persistence (mjoyce, mattmann)"
[master 208dde7] Fix for OODT-526: Add base functionality in Curator for Task
List persistence (mjoyce, mattmann)
5 files changed, 149 insertions(+), 7 deletions(-)
LMC-053601:oodt mattmann$ git push -u origin master
Counting objects: 39, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (22/22), done.
Writing objects: 100% (39/39), 4.66 KiB | 0 bytes/s, done.
Total 39 (delta 9), reused 0 (delta 0)
remote: oodt git commit: Fix for OODT-526: Add base functionality in Curator
for Task List persistence (mjoyce, mattmann)
To https://git-wip-us.apache.org/repos/asf/oodt.git
2ff8689..208dde7 master -> master
Branch master set up to track remote branch master from origin.
{noformat}
> Add base functionality in Curator for Task List persistence
> ---
>
> Key: OODT-526
> URL: https://issues.apache.org/jira/browse/OODT-526
> Project: OODT
> Issue Type: Sub-task
> Components: curator
>Reporter: Michael Joyce
>Assignee: Chris A. Mattmann
>Priority: Minor
> Fix For: 1.1
>
> Attachments: OODT-526-mjoyce-121105.patch.txt
>
>
> Make the task list export by default to a local file as starting point for
> future changes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (OODT-527) Add configuration options to Curator Task List persistence
[ https://issues.apache.org/jira/browse/OODT-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann resolved OODT-527. Resolution: Won't Fix unneeded, this is icing > Add configuration options to Curator Task List persistence > -- > > Key: OODT-527 > URL: https://issues.apache.org/jira/browse/OODT-527 > Project: OODT > Issue Type: Sub-task > Components: curator >Reporter: Michael Joyce >Assignee: Chris A. Mattmann >Priority: Minor > Fix For: 1.1 > > > Add config options for the Curator Task List persistence. > Turn persistence on/off > Destination of state information (local file, DB, etc) > Other? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (OODT-525) Export IngestTaskList from Curator
[
https://issues.apache.org/jira/browse/OODT-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann resolved OODT-525.
Resolution: Fixed
Thanks Mike!
{noformat}
LMC-053601:oodt mattmann$ git commit -m "Update Ingestion resource: OODT-525."
[master 2ff8689] Update Ingestion resource: OODT-525.
1 file changed, 4 insertions(+)
LMC-053601:oodt mattmann$ git push -u origin master
Counting objects: 14, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (8/8), done.
Writing objects: 100% (14/14), 1.11 KiB | 0 bytes/s, done.
Total 14 (delta 3), reused 0 (delta 0)
remote: oodt git commit: Update Ingestion resource: OODT-525.
To https://git-wip-us.apache.org/repos/asf/oodt.git
214fe8b..2ff8689 master -> master
Branch master set up to track remote branch master from origin.
LMC-053601:oodt mattmann$
{noformat}
> Export IngestTaskList from Curator
> --
>
> Key: OODT-525
> URL: https://issues.apache.org/jira/browse/OODT-525
> Project: OODT
> Issue Type: Sub-task
> Components: curator
>Reporter: Michael Joyce
>Assignee: Chris A. Mattmann
>Priority: Minor
> Fix For: 1.1
>
> Attachments: OODT-525.mjoyce.121029.patch.txt
>
>
> Allow the task list to be exported in a convenient format so the state can be
> stored across sessions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
