Page History

...

Finally, currently, multiple Solr cores are NOT supported: all documents sent by the File Manager are indexed and retrieved from the default Solr core.

Extension Points

----------------Currently, a File Manager deployment based on a Solr back-end can be customized in three two possible ways,
controlled by properties set in the File Manager filemgr.properties file. All Both extension points have reasonable
default implementations, which should be adequate in many cases, or at least to start experiment with this architecture.o

Generation of product unique identifiers

...

When a product is first ingested, a unique identifier must be created to reference that product in all subsequent requests.
The particular algorithm that is used to generate the identifier has great consequences for the underlying semantics of the
metadata catalog.

By default, the Solr File Manager will assign a newly generated UUID as the product unique identifier.
As a consequence, if the FM client sends the same physical product twice, two distinct records will be created in the Solr index.

Code Block
org.apache.oodt.cas.filemgr.catalog.solr.productIdGenerator=org.apache.oodt.cas.filemgr.catalog.solr.UUIDProductIdGenerator

Another possibility is to configure the Solr File Manager to use the product name as the unique identifier. In this case, if the
same product is ingested for a second time, the new Solr document will completely override the previous one, resulting in only
one product record in the catalog.

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

Alternatively, a project can provide a custom algorithm to generate product identifiers (for example, based on the system time
when the product is ingested) by implementing the ProductIdGenerator interface.

...