You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 5
Next »
The relationship between VIVO and Solr
What is Solr?
- A self-contained search application
- maintains its own index
- exists as a web application
- send it requests to
- search
- add, update, or delete records
- May live in the same Tomcat as VIVO, or may not
- Example Solr runs in Jetty
- Built on Lucene
- Open source
How does VIVO use Solr?
- The obvious is the search page
- Used internally when a search through the RDF would be too slow
How is the index kept up to date?
- When an individual is added/edited/deleted, Solr is given the new information and updates the index.
- Sometimes the index must be rebuilt
- The Solr home directory
- What is in it?
- How does Solr find it?
- How is it built?
- build script - Tomcat or otherwise.
- Need to tell VIVO how to contact Solr
- Authorization tests, now obsolete
- VIVO may start before Solr does. Usually does.
- Smoke tests
- Immediate failures
- Separate thread, since Solr may start after VIVO
- Go to the status page. Do you see a successful completion?
- No content
- Confirm that this is a Solr problem by navigating through VIVO and finding content.
- Others?
Is Solr working properly?
- Check the admin console.
- See the fields
- See the contents?
- Look in the Solr log
Does it help to rebuild?
- Really clean
- Solr home directory
- Tomcat/webapps, Tomcat/work, Tomcat/conf
- ant clean deploy (or ant all)
Is the communication working?
- Check the VIVO log?
- Check the deploy.properties (both in the log and in the file)