Cameron Goodale created OODT-487:
------------------------------------

             Summary: MetadataBasedProductMover to handle when the source and 
destinations match
                 Key: OODT-487
                 URL: https://issues.apache.org/jira/browse/OODT-487
             Project: OODT
          Issue Type: Improvement
          Components: file manager
    Affects Versions: 0.4
         Environment: OS X 10.6.8, CentOS 5
            Reporter: Cameron Goodale
            Assignee: Cameron Goodale
            Priority: Minor
             Fix For: 0.5


I was trying to move an entire ProductType using the MetadataBasedProductMover 
class.  Everything as going swell until it reached a product that was missing 
from the archive.  

When I restarted the move MetadataBasedProductMover started complaining about 
the source and destination for the move are the same, and it would halt with 
the following errors:

INFO: Moving product: [blah.txt] from: [/Users/cgoodale/files/moved/null] to: 
[/Users/cgoodale/files/moved/null]
Exception in thread "main" 
org.apache.oodt.cas.filemgr.structs.exceptions.DataTransferException: 
java.lang.Exception: 
org.apache.oodt.cas.filemgr.structs.exceptions.DataTransferException: cannot 
move product: [blah.txt] to same location: 
[file:/Users/cgoodale/files/moved/null]
        at 
org.apache.oodt.cas.filemgr.system.XmlRpcFileManagerClient.moveProduct(XmlRpcFileManagerClient.java:305)
        at 
org.apache.oodt.cas.filemgr.tools.MetadataBasedProductMover.moveProducts(MetadataBasedProductMover.java:113)
        at 
org.apache.oodt.cas.filemgr.tools.MetadataBasedProductMover.moveProducts(MetadataBasedProductMover.java:142)
        at 
org.apache.oodt.cas.filemgr.tools.MetadataBasedProductMover.main(MetadataBasedProductMover.java:172)

I have written up a small patch to MetadataBasedProductMover that does a check 
before attempting to perform the move.  Thanks to Michael Joyce for his help on 
this.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to