Mailing-List: contact dev-help@oodt.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@oodt.apache.org
Received-SPF: pass (athena.apache.org: local policy)
From: "Mattmann, Chris A (388J)" <chris.a.mattmann@jpl.nasa.gov>
To: "<dev@oodt.apache.org>" <dev@oodt.apache.org>
Subject: Re: Observation of the MetadataBasedProductMover
Thread-Topic: Observation of the MetadataBasedProductMover
Thread-Index: AQHNl0BztaWY+FcNyU2c5y+uHVDxzZeUtGaA
Date: Fri, 21 Sep 2012 05:01:31 +0000
Message-ID: <E3BAE5D6-9E9B-4981-B79B-5BF915633560@jpl.nasa.gov>
References: 
 <CADW5P+98kCngq81XwPapicE6YRWdvEG6vWq5JzwM3r0oYMv_sQ@mail.gmail.com>
In-Reply-To: 
 <CADW5P+98kCngq81XwPapicE6YRWdvEG6vWq5JzwM3r0oYMv_sQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A69E5B10EDD71B48A223131F2259FCE7@ad.jpl>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hey Cam,

Yep the FileLocation should indeed be kept in sync. I think that the Produc=
tMoverTool was constructed
without this in mind.=20

Can you open a JIRA issue and we can fix?

Thanks!

Cheers,
Chris

On Sep 20, 2012, at 7:51 AM, Cameron Goodale wrote:

> For anyone who needs to re-organize your OODT Archive I found this little
> tool to be quite useful.
>=20
> You can check out the code here:
> https://svn.apache.org/repos/asf/oodt/trunk/filemgr/src/main/java/org/apa=
che/oodt/cas/filemgr/tools/MetadataBasedProductMover.java
>=20
>=20
> 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.
>=20
> 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<product_type_repoPath:file:///usr/local/snow/data/archiv=
e>
> stored,omitNorms<product_type_versioner:gov.nasa.jpl.snow.versioning.Modi=
sFileVersioner>
> *
> stored,omitNorms<reference_data_store:file:/usr/local/snow/data/archive/M=
OD09GA/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>
> *
>=20
> So the question I am posing to the list is:  Should the FileLocation be
> kept in-sync with the reference_data_store?  If this should happen, then =
I
> think the MetadataBasedProductMover should be patched to make this update
> at the time of the move.
>=20
> Best Regards,
>=20
>=20
> Cameron


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++