Hi Chris, Thanks for your help! I didn't realize '--clientTransfer' was necessary, but I now got the metadata ingest to work.
Thanks! Rishi On Dec 28, 2010, at 5:26 PM, Mattmann, Chris A (388J) wrote: > Hi Rishi, > > >> The filemgr-client usage statement seems to indicate support only for >> (--clienTransfer or --dataTransfer) options, not the "--transferFactory" as >> you suggested. > > Sorry, I didn't know you interpreted my recollection of the *exact parameter > name* literally. YMMV doing that. The best bet will always be to check the > cmd line usage (with no args like you did) for the most up-to-date usage. > >> In any case though, I tried a couple parameter arguments with >> filemgr-client, but all yield an error saying a product specified with >> --refs could not be located: >> >> 1) ./filemgr-client ... --transferFactory InPlaceDataTransferFactory --refs >> file:///doesnotexist >> >> 2) ./filemgr-client ... --dataTransfer InPlaceDataTransferFactory --refs >> file:///doesnotexist >> >> 3) ./filemgr-client ... --dataTransfer >> org.apache.oodt.cas.filemgr.datatransfer.InPlaceDataTransfererFactory --refs >> file:///doesnotexist >> >> 4) ./filemgr-client ... --transferFactory InPlaceDataTransfer --refs >> file:///doesnotexist > > None of the above will would because they all omit the use of: > > --clientTransfer > NOTE: this parameter tells the File Manager that the FM Client will be doing > the actually data transferring, rather than the FM Server. > > So, basically what you do is you provide both the switch to turn on client > transfer *and* the appropriate data transfer factory. Try: > > --clientTransfer --dataTransfer > org.apache.oodt.cas.filemgr.datatransfer.InPlaceDataTransferFactory > > HTH! > > Cheers, > Chris > >> >> On Dec 28, 2010, at 2:12 PM, Chris A Mattmann wrote: >> >> Hi Rishi, >> >> Thanks. You just need to specify InPlaceDataTransfer as the >> --transferFactory parameter to the fmClient or to the crawler (which also >> expects a transfer factory)... >> >> Cheers, >> Chris >> >> On Dec 28, 2010, at 1:54 PM, Verma, Rishi (317I) wrote: >> >> Hi - >> >> Thanks for the helpful tips. >> >> I was looking at InPlaceDataTransferer, and it does not seem to have a >> command line interface (there's no main). Specifically, I looked at the class >> "org.apache.oodt.cas.filemgr.datatransfer.InPlaceDataTransferer" >> >> Is there a command-line wrapper already built I can use? >> >> Thanks again! >> Rishi >> >> >> On Dec 23, 2010, at 3:44 PM, holenoter wrote: >> >> >> sounds like a case for the profile/product server . . . but if you really >> want to use the filemgr, you can just use the InPlaceDataTransferer . . . if >> you mean by "i don't have the product on hand" meaning it is stored >> somewhere else, then just put that url where it is stored as the --ref arg . >> . . otherwise, if the product isn't anywhere, just put a random url as the >> arg to --ref (e.g. file:///some/file/i/dont/have) . . . it will at least let >> you get the metadata in >> >> -brian >> >> On Dec 23, 2010, at 2:28 PM, Verma, Rishi (317I) wrote: >> >> Hi everyone, >> >> I'm experimenting with OODT filemanager, and wanted to ingest a product >> file's met into the filemgr catalog. >> >> I don't have the product file on hand, but I do have the metadata. >> >> The filemgr user's guide (ie. >> http://oodt.apache.org/components/maven/filemgr/user/basic.html) documents >> how to ingest a product file assuming you actually have the product on hand. >> However, if I only want to ingest the metadata, how would I go about doing >> this? >> >> The 'filemgr-client' script seems to not allow ignoring the product >> reference. In other words, I cannot simply eliminate the "--refs" flag. >> >> >> ./filemgr-client --url http://localhost:9000 --operation \ >> --ingestProduct --productName blah.txt --productStructure Flat \ >> --productTypeName GenericFile \ >> --metadataFile file:///usr/local/cas-filemgr-v1.8.0/bin/blah.txt.met \ >> --refs file:///usr/local/cas-filemgr-v1.8.0/bin/blah.txt >> >> >> Any tips on how to ingest metadata only? >> >> Thanks! >> Rishi >> >> >> >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Senior Computer Scientist >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 171-266B, Mailstop: 171-246 >> Email: [email protected]<mailto:[email protected]> >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Assistant Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> > > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >
