-
Notifications
You must be signed in to change notification settings - Fork 3
SOLR Documentation
SOLR 8 Guide : https://solr.apache.org/guide/8_11/about-this-guide.html
solr.xml file prior to starting your servlet container.
$SOLR_HOME/lib
The solrconfig.xml file is the configuration file with the most parameters affecting Solr itself.
While configuring Solr, you’ll work with solrconfig.xml often, either directly or via the Config API to create "configuration overlays" (configoverlay.json) to override the values in solrconfig.xml.
In solrconfig.xml, you configure important features such as:
- request handlers, which process the requests to Solr, such as requests to add documents to the index or requests to return results for a query ** search :
*** qf and pf qf and pf are used by default, if not otherwise specified by client. The default blacklight_config will use these for the "keywords" search.
author_qf/author_pf, title_qf which the default blacklight_config will specify for those searches.
*** defType **** disMax *** facet *** spellcheck
-
updateHandler : Determines index updates through commits. Items are not searchable until they are committed.
-
Datadir and directoryFactory : Where and how Solr stores its indexes are configurable options.
-
listeners, processes that "listen" for particular query-related events; listeners can be used to trigger the execution of special code, such as invoking some common queries to warm-up caches
-
the Request Dispatcher for managing HTTP communications
The solrconfig.xml file is located in the conf/ directory for each collection. Several well-commented example files can be found in the server/solr/configsets/ directories demonstrating best practices for many different types of installations. /var/solr
Solr Uses Managed Schema by Default When a is not explicitly declared in a solrconfig.xml file, Solr implicitly uses a ManagedIndexSchemaFactory, which is by default "mutable" and keeps schema information in a managed-schema file.
true managed-schema If you wish to explicitly configure ManagedIndexSchemaFactory the following options are available:mutable - controls whether changes may be made to the Schema data. This must be set to true to allow edits to be made with the Schema API.
managedSchemaResourceName is an optional parameter that defaults to "managed-schema", and defines a new name for the schema file that can be anything other than “schema.xml”.
With the default configuration shown above, you can use the Schema API to modify the schema as much as you want, and then later change the value of mutable to false if you wish to "lock" the schema in place and prevent future changes.
Classic schema.xml An alternative to using a managed schema is to explicitly configure a ClassicIndexSchemaFactory. ClassicIndexSchemaFactory requires the use of a schema.xml configuration file, and disallows any programatic changes to the Schema at run time. The schema.xml file must be edited manually and is only loaded only when the collection is loaded.
Switching from schema.xml to Managed Schema If you have an existing Solr collection that uses ClassicIndexSchemaFactory, and you wish to convert to use a managed schema, you can simply modify the solrconfig.xml to specify the use of the ManagedIndexSchemaFactory.Once Solr is restarted and it detects that a schema.xml file exists, but the managedSchemaResourceName file (i.e., “managed-schema”) does not exist, the existing schema.xml file will be renamed to schema.xml.bak and the contents are re-written to the managed schema file. If you look at the resulting file, you’ll see this at the top of the page:
You are now free to use the Schema API as much as you want to make changes, and remove the schema.xml.bak.
/opt/solr
Logger Core Admin Query
https://github.com/projectblacklight/blacklight/wiki/Indexing-your-data-into-solr
class MyModel < ActiveRecord::Base after_save :index_record before_destroy :remove_from_index
attr_accessible :field_i_want_to_index
def to_solr
# *_texts here is a dynamic field type specified in solrconfig.xml
{'id' => id,
'field_i_want_to_index_texts' => field_i_want_to_index}
end
def index_record
SolrService.add(self.to_solr)
SolrService.commit
end
def remove_from_index
SolrService.delete_by_id(self.id)
SolrService.commit
end
end
/app/controllers/catalog_controller.rb (page per sort, fields to search, sort fields)
https://github.com/projectblacklight/blacklight/wiki/Configuration---Solr-fields
- Set a FREEZE on Scholar content.
- Deploy cap deploy prod
- Login into Web Server
- Change Login Route /login /error (both web servers)
- Run rake hyrax:count RAILS_ENV=Production to get a count of all works in each work type.
- Run rake scholar:pidsout RAILS_ENV=Production
- Login into Solr Server
- As the root user, stop solr with service solr stop
- Back up /var/solr to ... tar -cvf solr.tar solr
- CD /opt
- Delete the existing /opt/solr symlink... rm solr
- Download solr-8.11.1.tgz from https://solr.apache.org/downloads.html
- Uncompress solr-8.11.1.tgz to /opt/solr-8.11.1
- Create a new symlink for /opt/solr-8.11.1 to /opt/solr.... ln -s solr-8.11.1 solr
- As the root user, start solo with service solr start
- Delete everything from SOLR using the CURL command
- curl http://localhost:8983/solr/collection1/update?commit=true -H "Content-Type: text/xml" --data-binary ':'
- Login into Web Server
- bundle exec rails console production on web server
- Run solr reindex (ActiveFedora::Base.reindex_everything)
- If reindex doesn’t run than you need to create a new core on solr with the existing name pointing to the correct xml files
- If there is anything wrong with the results, then run rake scholar:resave
- Run rake hyrax:count to get a count of all works in each work type and compare results.
- Confirm upgrade was successful and release the FREEZE.
https://www.nopio.com/blog/create-search-application-blacklight/ https://solr.apache.org/guide/solr/latest/getting-started/solr-tutorial.html https://www.solrtutorial.com/solr-in-5-minutes.html