Page History

...

Alternatively, a project may provide its own product generation algorithm by implementing the ProductDeserializer interface, in a way that is consistent with its own implementation of the ProductSerializer interface.

Configuration

-------------The deployment of a Solr File Manager is controlled by two main files: the File Manager filemgr.properties, and the Solr schema.xml.>>> File Manager

filemgr.properties

To use a Solr-based metadata catalog, the File Manager file filemgr.properties must be edited as follows. 

At a minimum the following two properties must be defined:o

• org.apache.oodt.cas.filemgr.catalog.factory=org.apache.oodt.cas.filemgr.catalog.solr.SolrCatalogFactory
  • mandatory: instructs OODT to instantiate a Solr Catalog implementation at startup# mandatory: instructs OODT to instantiate a Solr Catalog implementation at startup

...

• org.apache.oodt.cas.filemgr.catalog.solr.url=http://<hostname>:<port>/solr
  • mandatory: points the File Manager to the base URL of the Solr

...

• • server 

Additionally, the following properties control how products are ingested and extracted into/from the Solr server,
i.e. the implementation implementations used for the extension points described above. These properties have default values,
and need to be set only when the default is not the desired behavior.o

• org.apache.oodt.cas.filemgr.catalog.solr.productIdGenerator=org.apache.oodt.cas.filemgr.catalog.solr.UUIDProductIdGenerator

  ...

  • • optional: controls the algorithm for generating the product unique identifier when it is first stored in the catalog.
    • default: UUIDProductIdGenerator: this class generates a new UUID every time a product is indexed.
    • alternative out of the box implementation: NameProductIdGenerator: this class will assign the product an identifier equal to the product name.
    • alternatively: provide any custom implementation of the ProductIdGenerator interface.

  ...

  • org.apache.oodt.cas.filemgr.catalog.solr.productSerializer=org.apache.oodt.cas.filemgr.catalog.solr.DefaultProductSerializer

  optional: controls the format of the documents ingested into Solr, i.e. how a CAS product object is transformed into one (or more) Solr records.
  default: DefaultProductSerializer: creates one Solr record for each incoming CAS product:
  -) the product core attributes (id, name, type) are converted to Solr fields starting with "CAS." ("CAS.ProductId", "CAS.ProductName", ....)
  -) the product identifier is used again to assign the Solr record identifier (i.e. "id" and "CAS.ProductId" have the same value)
  -) the product references are converted into Solr fields starting with ("CAS.reference..." or "CAS.root.reference...")
  -) the product metadata attributes are converted into Solr fields with the same name and number of values
  Alternative: any custom implementation of the ProductSerializer interface can be used.
  Note that each specific implementation of ProductSerializer must declare the format of the generated Solr documents (XML, JSON, etc.),
  so each implementation is free to generate Solr documents in the document rormat of choice.

  ...