Hi John, What beau on of OODT are you using? The file types should be encapsulated by the factory implementation I would guess. It should be. Case of mike this the default filemgr store then off you go. Can you provide a paste of how your arriving at your exception please? Lewia
On Wednesday, March 11, 2015, John Reynolds <[email protected]> wrote: > Should S3DataTransferer work with the generic file type from the get go or > is there anything i need to change > i was using the radix docker but getting 'Caused by: > java.security.NoSuchAlgorithmException: Algorithm HmacSHA1 not available’ > i tried downloading the jce but no dice > i might try just building on my local machine and trying again > > Thanks > > > On Mar 10, 2015, at 6:19 PM, Lewis John Mcgibbney < > [email protected] <javascript:;>> wrote: > > > > Hey John, > > You're right, you've nearly answered everything here ;) > > OK, so your properties can be located here > > > https://github.com/apache/oodt/blob/trunk/filemgr/src/main/resources/filemgr.properties#L114-L124 > > You'll see the usual key, value pairs in there which you can ad before > > build the project and packaging filemgr.properties along with your > compiled > > code. > > Regarding the following, > > > > On Tue, Mar 10, 2015 at 4:31 PM, John Reynolds <[email protected] > <javascript:;>> wrote: > > > >> > >> in the near future, i will want to pass in a security token as well to > the > >> S3 client. to do so i would extend or modify the s3datatransfer class > >> (which expires after an hour), what’s the best practice to read in this > >> transient data from the command line (or wherever else i would initiate > a > >> job from) since this wouldnt go in a properties file > > > > > > Do you mean that your security token expires hourly? As oppose to your s3 > > client? > > Lets try and defined exactly what you are after here. > > Thanks > > Lewis > > -- *Lewis*
