DEPRECATION WARNING
This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
Index Maintenance¶
Solr offers a lot of request handlers to do maintenance tasks.
Committing pending documents¶
curl http://host:port/solr-path/update -H "Content-Type: text/xml"
--data-binary '<commit />'
Clearing the index¶
curl http://host:port/solr-path/update -H "Content-Type: text/xml"
--data-binary '<delete><query>*:*</query></delete>'
curl http://host:port/solr-path/update -H "Content-Type: text/xml"
--data-binary '<commit />'
Optimizing the index¶
You should do this every once in a while, f.e. every day. For TYPO3, there is already a scheduler task available for this.
curl http://host:port/solr-path/update -H "Content-Type: text/xml"
--data-binary '<optimize />'
Searching the index from the command line¶
Parameters:
q: | what to search for. Format: fieldName:fieldValue |
---|---|
qt: | defines the query type, for the command line we recommend "standard", the extension itself uses "dismax" |
fl: | comma separated list of fields to return |
rows: | number of rows to return |
start: | offset from where to return results |
curl 'http://host:port/path-to-solr/select?q=hello&qt=standard&fl=title,content'
Create cores with the core admin api¶
The CoreAdmin API (https://cwiki.apache.org/confluence/display/solr/CoreAdmin+API) allows you, manipulate the cores in your solr server.
Since we support configSets a core could be generated with the following http call:
curl 'http://host:port/path-to-solr/admin/cores?action=CREATE&name=core_de&configSet=ext_solr_6_0_0&schema=german/schema.xml&dataDir=dataDir=../../data/german'