Chris, Another question comes up. If I apply MappedDataSourceCatalog, will this work with the flat database tables implementation aka ColumnBasedDataSourceCatalog?
Thanks, Cynthia On 6/5/12 6:51 AM, "Wong, Cynthia L (388J)" <[email protected]> wrote: >Chris, > >Thank you for looking up the information. This does provide a solution >that I'm looking for. > >Cynthia > >On 6/4/12 10:03 PM, "Mattmann, Chris A (388J)" ><[email protected]> wrote: > >>[cc /Apache lists] >> >>Hey Cynthia, >> >>See this file: >> >>http://s.apache.org/Tds >> >>Pretty self-explanatory really. The left side is the Product Type name >>and the right >>side of the equals sign is the mapped Oracle table name. If you define a >>mapping >>in this file it will be used, otherwise the default >>ProductTypeName_reference >>and ProductTypeName_metadata will be used. >> >>To enable the catalog, per http://s.apache.org/Jkh >> >>Change: >> >># catalog factory >>filemgr.catalog.factory=org.apache.oodt.cas.filemgr.catalog.LuceneCatalog >>F >>actory >> >>to: >> >># catalog factory >>filemgr.catalog.factory=org.apache.oodt.cas.filemgr.catalog.MappedDataSou >>r >>ceCatalogFactory >> >>And then set: >> >># mapped data source catalog configuration >>org.apache.oodt.cas.filemgr.catalog.mappeddatasource.mapFile=/path/to/ops >>. >>catalog.typemap.properties >> >>The existing data source properties (JDBC url, etc.) will be inherited >>from the default >>DataSourceCatalog properties. >> >>HTH! >> >>Cheers, >>Chris >> >> >>On Jun 4, 2012, at 3:29 PM, Wong, Cynthia L (388J) wrote: >> >>> Chris, >>> >>> That's good to know. Is there any example that shows how to use and set >>>up >>> MappedDataSourceCatalog? However, we actually would like to avoid >>> maintaining the mapping. Can we apply MappedDataSourceCatalog only to >>>the >>> long product type names and not other types? >>> >>> Thanks, >>> Cynthia >>> >>> >>> >>> On 6/4/12 3:00 PM, "Mattmann, Chris A (388J)" >>> <[email protected]> wrote: >>> >>>> Hi Cynthia, >>>> >>>> Scope out the MappedDataSourceCatalog :) >>>> >>>> It will get you around this... >>>> >>>> Cheers, >>>> Chris >>>> >>>> On Jun 4, 2012, at 2:17 PM, Wong, Cynthia L (388J) wrote: >>>> >>>>> Hello, all, >>>>> >>>>> We've recently switched from MySQL to Oracle. Migrating the File >>>>> Catalog from MySQL to Oracle has triggered a problem. Oracle has a >>>>> limitation of 30 characters for table names. File Manager's >>>>> implementation assign table names as the following: >>>>> >>>>> [Product Type Name]_REFERENCE for tracking location references of the >>>>> stored files >>>>> [Product Type Name]_METADATA for metadata about stored files >>>>> >>>>> Note that "_REFERENCE" contains 10 characters already and therefore >>>>> there is a limitation of 20 characters for ProductTypeName. I'm >>>>> wondering if anyone has encountered this restriction. Is there a >>>>> workaround? >>>>> >>>>> Thanks, >>>>> Cynthia >>>>> >>>>> >>>> >>>> >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>> 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 >>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>>> >>>> >>> >>> >> >> >>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>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 >>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >
