You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by ma...@apache.org on 2011/04/19 03:54:23 UTC

svn commit: r1094840 - in /oodt/trunk: CHANGES.txt metadata/src/main/resources/examples/extern-config.xml

Author: mattmann
Date: Tue Apr 19 01:54:23 2011
New Revision: 1094840

URL: http://svn.apache.org/viewvc?rev=1094840&view=rev
Log:
- fix for OODT-181 Add documentation for metFileExt attribute on exec element in ExternMetExtractor

Modified:
    oodt/trunk/CHANGES.txt
    oodt/trunk/metadata/src/main/resources/examples/extern-config.xml

Modified: oodt/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/oodt/trunk/CHANGES.txt?rev=1094840&r1=1094839&r2=1094840&view=diff
==============================================================================
--- oodt/trunk/CHANGES.txt (original)
+++ oodt/trunk/CHANGES.txt Tue Apr 19 01:54:23 2011
@@ -4,6 +4,9 @@ Apache OODT Change Log
 Release 0.3-SNAPSHOT (in progress)
 --------------------------------------------
 
+* OODT-181 Add documentation for metFileExt attribute on exec element in
+  ExternMetExtractor (mattmann)
+
 * OODT-179 Upgrade PushPull FTP protocol to use Commons Net 2.2 (mattmann)
 
 * OODT-176 Baked in file manager policy should include example of product type metadata (mattmann)

Modified: oodt/trunk/metadata/src/main/resources/examples/extern-config.xml
URL: http://svn.apache.org/viewvc/oodt/trunk/metadata/src/main/resources/examples/extern-config.xml?rev=1094840&r1=1094839&r2=1094840&view=diff
==============================================================================
--- oodt/trunk/metadata/src/main/resources/examples/extern-config.xml (original)
+++ oodt/trunk/metadata/src/main/resources/examples/extern-config.xml Tue Apr 19 01:54:23 2011
@@ -27,8 +27,13 @@ the License.
 	    the .met file will be generated in /path/to/file's parent directory. Otherwise, if the
 	    external command let met extractor doesn't honor working dir, then all bets
 	    are off.
+	    
+	    metFileExt: specifies the file extension for the extern met extractor to look for when 
+	    reading the generated met file into Java as an in-memory CAS metadata object. The met 
+	    file extension is appended to the full file path of the original data file. If not specified, 
+	    then the met file extension defaults to ".met".
 	-->
-	<exec workingDir="">
+	<exec workingDir="" metFileExt="">
 		<!--  this path can be absolute or relative -->
 		<!--  you can optionally specify envReplace tag (=true) 
 		      to turn on environment variable replacement
@@ -61,8 +66,15 @@ the License.
 			      is not called. If called, all white spaces are replaced from the path
 			      (using the above regex), and replaced with the literal string
 			      "\ ".
+			      
+			      The appendExt parameter is used to augment an existing argument 
+			      with some specified extension. This is typically used on paths 
+			      to add another extension to an argument that's a path. For instance, 
+			      you could append the .cas metadata file extension to an existing 
+			      path, e.g., the data file path.
 			-->
 			<arg envReplace="true" isPath="true">[HOME]/test boo</arg>
+			<arg appendExt="cas">/full/path/to/somefile.txt</arg>
 		</args>
 	</exec>