You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "John J. Tran (JIRA)" <ji...@apache.org> on 2011/07/19 21:30:58 UTC
[jira] [Closed] (OODT-300) Product Type misconfiguration
[ https://issues.apache.org/jira/browse/OODT-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John J. Tran closed OODT-300.
-----------------------------
Resolution: Not A Problem
After speaking with Chris Mattmann, this is really not an issue because we have to specify the producttype with the default extractor
> Product Type misconfiguration
> -----------------------------
>
> Key: OODT-300
> URL: https://issues.apache.org/jira/browse/OODT-300
> Project: OODT
> Issue Type: Bug
> Components: curator
> Affects Versions: 0.3
> Reporter: John J. Tran
> Labels: curation
> Fix For: 0.4
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> It seems like there is a possible bug with the ecas curator:
> http://svn.apache.org/viewvc/oodt/tags/0.3/curator/src/main/java/org/apache/oodt/cas/curation/service/MetadataResource.java?view=markup
> refers to PRODUCT_TYPE key as "productType" -- however, else is used as "ProductType", for example
> http://svn.apache.org/viewvc/oodt/trunk/filemgr/src/main/java/org/apache/oodt/cas/filemgr/metadata/CoreMetKeys.java?view=markup
> Also, in
> http://svn.apache.org/viewvc/oodt/trunk/curator/src/main/java/org/apache/oodt/cas/curation/service/IngestionResource.java?view=markup
> It seems that fileMet should set PRODUCT_TYPE to task.getProductType()
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira