Page History

...

• 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# mandatoryMandatory: instructs OODT to instantiate a Solr Catalog implementation at startup
• org.apache.oodt.cas.filemgr.catalog.solr.url=http://<hostname>:<port>/solr
  • mandatoryMandatory: points the File Manager to the base URL of the Solr server 

...

• org.apache.oodt.cas.filemgr.catalog.solr.productIdGenerator=org.apache.oodt.cas.filemgr.catalog.solr.UUIDProductIdGenerator
  • optionalOptional: controls the algorithm for generating the product unique identifier when it is first stored in the catalog.
  • defaultDefault: UUIDProductIdGenerator: this class generates a new UUID every time a product is indexed.
  • alternative Alternative out of the box implementation: NameProductIdGenerator: this class will assign the product an identifier equal to the product name.
  • alternativelyAlternatively: 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

  ...

  • • ; and vice-versa how CAS products are queried back from the Solr index
    • 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.

    ...

    • • • RootReference...")

    ...

    • • • the product metadata attributes are converted into Solr fields with the same name and number of

    ...

    • • • valu
      • 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 it understands (XML, JSON, etc.),
    so  so each implementation is free to generate and parse Solr documents in the document rormat format of choice.

    o org.apache.oodt.cas.filemgr.catalog.solr.productDeserializer=org.apache.oodt.cas.filemgr.catalog.solr.DefaultProductDeserializer
    optional: controls how CAS products are queried back from the Solr index.
    default: DefaultProductDeserializer: creates one CAS product for each returned Solr record, based on reversing the rules that created that record
    in the first place (see DefaultProductSerializer).
    Alternative: any custom implementation of the ProductDeserializer interface can be used,
    but it should be consistent with the specific implementation used for the ProductSerializer implementation.
    Note that each specific implementation of ProductDeserializer must declare the format of the Solr response documents it can parse (XML, JSON, etc.),
    so each implementation is free to parse the document format of choice.

    Example of full Following is a full example of Solr File Manager configuration (with default behavior):

    Code Block
    org.apache.oodt.cas.filemgr.catalog.factory=org.apache.oodt.cas.filemgr.catalog.solr.SolrCatalogFactory

    ...

    org.apache.oodt.cas.filemgr.catalog.solr.url=http://localhost:8983/solr

    ...

    org.apache.oodt.cas.filemgr.catalog.solr.productIdGenerator=org.apache.oodt.cas.filemgr.catalog.solr.NameProductIdGenerator

    ...

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

    ...

    ...

    schema.xml

    The file schema.xml, part of each specific Solr deployment, defines which metadata fields are stored in the Solr index, and can consequently be queried
    and retrieved by clients. Note that no metadata field can be ingested in Solr unless it is defined (explicitely or implicitely) in schema.xml.
    Additionally, a specific requirement of the File Manager - Solr integration is that each metadata field included in schema.xml must be "stored" (i.e.
    defined with stored="true"), so that it can be retrieved and re-inserted during partial document updates.

    ...