Info |
---|
This guide is meant to get someone up and running with a Fedora 4 instance whose updates are automatically indexed in a Solr repository. This guide glosses over many of the working details and should just be considered a starting point for testing this feature. The document assumes a posix POSIX operating system with curl, a text editor, java, git, and a download of apache solr Apache Solr 4.6.0. |
Install and Start Fedora 4
This guide assumes Fedora 4 is running on port 8080 with a jms port of 61616(with JMS listening on port 61616).
Install, Configure and Start Solr
...
Warning |
---|
The fcrepo-jms-indexer-pluggable SolrIndexer implementation does not commit upon updates. In order to see the changes, you must configure solr Solr to have a commit strategy that is appropriate for your use. Node removal events do trigger a commit. |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
<!-- AutoCommit Perform a hard commit automatically under certain conditions. Instead of enabling autoCommit, consider using "commitWithin" when adding documents. http://wiki.apache.org/solr/UpdateXmlMessages maxDocs - Maximum number of documents to add since the last commit before automatically triggering a new commit. maxTime - Maximum amount of time in ms that is allowed to pass since a document was added before automatically triggering a new commit. openSearcher - if false, the commit causes recent index changes to be flushed to stable storage, but does not cause a new searcher to be opened to make those changes visible. If the updateLog is enabled, then it's highly recommended to have some sort of hard autoCommit to limit the log size. --> <autoCommit> <maxTime>${solr.autoCommit.maxTime:15000}</maxTime> <openSearcher>false</openSearcher> </autoCommit> |
Start solr Solr and verify that it is running at http://localhost:8983/solr.
...
Ensure that the records are committed to solr Solr (either through an explicit commit or waiting until the configured commit period is up) and then see verify that they show up.