Lewis in general the one.X line of OODT products is cut from the master branch however the one.2.X is a series of patch releases to the one.2 branch so in this case we don’t have a problem and that’s why the Avro stuff was not part of it
Sent from my iPhone > On Sep 19, 2018, at 1:56 PM, lewis john mcgibbney <lewi...@apache.org> wrote: > > Hi Chris, > Thanks for chiming in. > IIRC, the 1.X line of releases is cut from master, is that correct? > If so, then master contains Avro implementations, for example > https://github.com/apache/oodt/tree/master/filemgr/src/main/java/org/apache/oodt/cas/filemgr/system > You will see the legacy XmlRpc implementations as well as the newer AvroRpc > implementations. > The same is true for resource and workflow > https://github.com/apache/oodt/tree/master/resource/src/main/java/org/apache/oodt/cas/resource/system > https://github.com/apache/oodt/tree/master/workflow/src/main/java/org/apache/oodt/cas/workflow/system > > The issue I am having is that AFAICT, these classes are not included within > the 1.2.5 release JAR's. > > Can anyone else confirm? Thanks Chris for any insight. > Lewis > >> On Tue, Sep 18, 2018 at 6:44 PM <dev-digest-h...@oodt.apache.org> wrote: >> >> >> dev Digest 19 Sep 2018 01:44:13 -0000 Issue 1318 >> >> Topics (messages 8475 through 8477) >> >> Re: AvroRpc Classes not included in 1.2.5 release artifacts >> 8475 by: Mattmann, Chris A (1761) >> >> Best Place to Augment ENVI Header Metadata >> 8476 by: lewis john mcgibbney >> >> [ANNOUNCE] Apache OODT 1.2.5 released >> 8477 by: Tom Barber >> >> Administrivia: >> >> --------------------------------------------------------------------- >> To post to the list, e-mail: dev@oodt.apache.org >> To unsubscribe, e-mail: dev-digest-unsubscr...@oodt.apache.org >> For additional commands, e-mail: dev-digest-h...@oodt.apache.org >> >> ---------------------------------------------------------------------- >> >> >> >> >> ---------- Forwarded message ---------- >> From: "Mattmann, Chris A (1761)" <chris.a.mattm...@jpl.nasa.gov> >> To: "dev@oodt.apache.org" <dev@oodt.apache.org> >> Cc: >> Bcc: >> Date: Mon, 17 Sep 2018 01:20:55 +0000 >> Subject: Re: AvroRpc Classes not included in 1.2.5 release artifacts >> It is correct since it is off the 1.2.x branch. Avro is in 1.9-SNAP and >> later >> >> Sent from my iPhone >> >>> On Sep 16, 2018, at 4:49 PM, lewis john mcgibbney <lewi...@apache.org> >> wrote: >>> >>> Hi Folks, >>> Executing the following >>> >>> jar -tf workflow/lib/cas-workflow-1.2.5.jar >>> >>> There is no entry for the AvroRpc* functionality. This is not correct and >>> we need to make sure the Avro material is included in the next release as >>> it is merged into master. >>> >>> Lewis >>> >>> -- >>> http://home.apache.org/~lewismc/ >>> http://people.apache.org/keys/committer/lewismc >> >> >> >> >> ---------- Forwarded message ---------- >> From: lewis john mcgibbney <lewi...@apache.org> >> To: dev@oodt.apache.org >> Cc: Coal-capstone <coal-capst...@googlegroups.com> >> Bcc: >> Date: Mon, 17 Sep 2018 10:48:55 -0700 >> Subject: Best Place to Augment ENVI Header Metadata >> Hi Folks, >> I have a typical ENVI header metadata file with the following values >> >> ENVI >> description = { >> Georeferenced Image built from input GLT. [Tue Aug 11 15:39:46 2015] [Tue >> Aug 11 16:17:51 2015]} >> samples = 1363 >> lines = 22826 >> bands = 432 >> header offset = 0 >> file type = ENVI Standard >> data type = 4 >> interleave = bil >> sensor type = Unknown >> byte order = 0 >> map info = { UTM , 1.000 , 1.000 , 201603.137 , 4061363.983 , >> 2.7000000000e+00 , 2.7000000000e+00 , 13 , North , WGS-84 , units=Meters , >> rotation=90.00000000 } >> wavelength units = Nanometers >> ... >> >> Before I work on Workflow and automating data staging and ingest, right >> now, I use the following syntax to ingest the file >> >> ./filemgr-client --operation --ingestProduct --productName >> ang20150420t182050_corr_v1e_img.hdr --productStructure Flat >> --productTypeName GenericFile --metadataFile >> >> file:///usr/local/coal-sds-deploy/data/staging/ang20150420t182050_corr_v1e_img.hdr.met >> --refs >> >> file:///usr/local/coal-sds-deploy/data/staging/ang20150420t182050_corr_v1e_img.hdr >> --url http://localhost:9000 >> >> This generates the following record >> >> { "id": "07193c17-67f8-4f8c-ac2e-5a281c7ee48c", "CAS.ProductStructure": >> "Flat", "CAS.ProductTypeName": "GenericFile", "CAS.ProductName": >> "ang20150419t155032_corr_v1f_img.hdr", "CAS.ProductReceivedTime": >> "2018-09-16T19:26:52Z", "CAS.ProductTypeId": "urn:oodt:GenericFile", " >> CAS.ProductTransferStatus": "RECEIVED", "CAS.ProductId": >> "07193c17-67f8-4f8c-ac2e-5a281c7ee48c", "FileLocation": [ >> >> "/usr/local/coal-sds-deploy/data/archive/ang20150419t155032_corr_v1f_img.hdr" >> ], "Filename": [ "ang20150419t155032_corr_v1f_img.hdr" ], "MimeType": [ >> "application/octet-stream", "application", "octet-stream" ], " >> CAS.ReferenceMimeType": [ "application/octet-stream" ], " >> CAS.ReferenceDatastore": [ >> >> "file:/usr/local/coal-sds-deploy/data/archive/ang20150419t155032_corr_v1f_img.hdr/ang20150419t155032_corr_v1f_img.hdr" >> ], "CAS.ReferenceFileSize": [ 20732 ], "CAS.ReferenceOriginal": [ >> >> "file:///usr/local/coal-sds-deploy/data/staging/ang20150419t155032_corr_v1f_img.hdr" >> ], "_version_": 1611819870151770000 } >> >> I would now like to also extract out the various values included within the >> file as top level metadata. How can I ensure that 1) the Tika extractor is >> being used to extract metadata and 2) that if Tika does not pick up the >> metadata, then I can pick it up some other way? Preferably this would be >> done server-side such that the client arguments are simple. >> >> Thanks >> Lewis >> >> -- >> http://home.apache.org/~lewismc/ >> http://people.apache.org/keys/committer/lewismc >> >> >> >> ---------- Forwarded message ---------- >> From: Tom Barber <magicaltr...@apache.org> >> To: annou...@apache.org, dev@oodt.apache.org >> Cc: >> Bcc: >> Date: Mon, 17 Sep 2018 22:47:34 +0100 >> Subject: [ANNOUNCE] Apache OODT 1.2.5 released >> The Apache OODT project is pleased to announce the release of Apache OODT >> 1.2.5. The release contents have been pushed out to the main Apache release >> site and to the Maven Central sync, so the releases should be available as >> soon as the mirrors get the syncs. >> >> Apache OODT is a software framework as well as an architectural style for >> the rapid construction of scientific data systems. It provides components >> for data capture, curation, metadata extraction, workflow management, >> resource management, and data processing. >> >> Apache OODT 1.2.5 contains a number of improvements and bug fixes. Details >> can be found in the changes file: >> http://www.apache.org/dist/oodt/CHANGES-1.2.5.txt >> >> Apache OODT is available in source form from the following download page: >> http://www-us.apache.org/dist/oodt/apache-oodt-1.2.5-src.zip >> >> Apache OODT is also available in binary form or for use using Maven 2 from >> the Central Repository: http://repo1.maven.org/maven2/org/apache/oodt/ >> >> In the initial 48 hours, the release may not be available on all mirrors. >> When downloading from a mirror site, please remember to verify the >> downloads using signatures found on the Apache site: >> https://people.apache.org/keys/group/oodt.asc >> For more information on Apache OODT, visit the project home page: >> http://oodt.apache.org/ >> >> -- Tom Barber, on behalf of the Apache OODT community >> >> -- >> >> >> Spicule Limited is registered in England & Wales. Company Number: >> 09954122. Registered office: First Floor, Telecom House, 125-135 Preston >> Road, Brighton, England, BN1 6AF. VAT No. 251478891. >> >> >> >> >> All engagements >> are subject to Spicule Terms and Conditions of Business. This email and >> its >> contents are intended solely for the individual to whom it is addressed >> and >> may contain information that is confidential, privileged or otherwise >> protected from disclosure, distributing or copying. Any views or opinions >> presented in this email are solely those of the author and do not >> necessarily represent those of Spicule Limited. The company accepts no >> liability for any damage caused by any virus transmitted by this email. If >> you have received this message in error, please notify us immediately by >> reply email before deleting it from your system. Service of legal notice >> cannot be effected on Spicule Limited by email. >> > > > -- > http://home.apache.org/~lewismc/ > http://people.apache.org/keys/committer/lewismc
