Cameron Goodale created OODT-509:
------------------------------------
Summary: MetadataBasedProductMover will Update the FileLocation
Metadata
Key: OODT-509
URL: https://issues.apache.org/jira/browse/OODT-509
Project: OODT
Issue Type: Bug
Components: file manager
Affects Versions: 0.4
Environment: CentOS 5
Reporter: Cameron Goodale
Assignee: Cameron Goodale
I have moved a lot of product using this tool, but I found a minor
inconsistency and I wanted to see if this is a bug. You see in the index
output listed below the FileLocation doesn't match the newly updated
reference_data_store, but it does match the reference_orig path.
stored,indexed<CAS.ProductId:413e8ad6-9dd8-11e1-be66-9f8d45bb9efe>
stored,indexed<CAS.ProductName:MOD09GA.A2010046.h21v04.005.2010048120042.hdf>
stored,indexed<CAS.ProductReceivedTime:2012-05-14T08:19:53.095-07:00>
stored,indexed<FileLocation:/usr/local/snow/data/archive/2010/46/MOD09GA>
stored,indexed<Filename:MOD09GA.A2010046.h21v04.005.2010048120042.hdf>
stored,omitNorms<reference_data_store:file:/usr/local/snow/data/archive/MOD09GA/2010/46/MOD09GA.A2010046.h21v04.005.2010048120042.hdf>
stored,omitNorms<reference_fileSize:90060629>
stored,indexed<reference_mimeType:application/x-hdf>
stored,omitNorms<reference_orig:file:/usr/local/snow/data/archive/2010/46/MOD09GA/MOD09GA.A2010046.h21v04.005.2010048120042.hdf>
Basically the fix would be to update the FileLocation Value when the
reference_data_store is updated.
--
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
