11.05.2016 Views

Apache Solr Reference Guide Covering Apache Solr 6.0

21SiXmO

21SiXmO

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

RELOAD<br />

The RELOAD action loads a new core from the configuration of an existing, registered <strong>Solr</strong> core. While the new<br />

core is initializing, the existing one will continue to handle requests. When the new <strong>Solr</strong> core is ready, it takes<br />

over and the old core is unloaded.<br />

http://localhost:8983/solr/admin/cores?action=RELOAD&core=core0<br />

This is useful when you've made changes to a <strong>Solr</strong> core's configuration on disk, such as adding new field<br />

definitions. Calling the RELOAD action lets you apply the new configuration without having to restart the Web<br />

container.<br />

RELOAD performs "live" reloads of <strong>Solr</strong>Core, reusing some existing objects. Some configuration options,<br />

such as the dataDir location and IndexWriter-related settings in solrconfig.xml can not be<br />

changed and made active with a simple RELOAD action.<br />

Input<br />

Query Parameters<br />

Parameter Type Required Default Description<br />

core string Yes N/A The name of the core, as listed in the "name" attribute of a element in solr.xml.<br />

RENAME<br />

The RENAME action changes the name of a <strong>Solr</strong> core.<br />

Input<br />

http://localhost:8983/solr/admin/cores?action=RENAME&core=core0&other=core5<br />

Query Parameters<br />

Parameter Type Required Default Description<br />

core string Yes The name of the <strong>Solr</strong> core to be renamed.<br />

other string Yes The new name for the <strong>Solr</strong> core. If the persistent attribute of is true, the new name will be written to solr.xml as the nam<br />

e attribute of the attribute.<br />

async string No Request ID to track this action which will be processed<br />

asynchronously<br />

SWAP<br />

SWAP atomically swaps the names used to access two existing <strong>Solr</strong> cores. This can be used to swap new content<br />

into production. The prior core remains available and can be swapped back, if necessary. Each core will be<br />

known by the name of the other, after the swap.<br />

http://localhost:8983/solr/admin/cores?action=SWAP&core=core1&other=core0<br />

Do not use SWAP with a <strong>Solr</strong>Cloud node. It is not supported and can result in the core being unusable.<br />

<strong>Apache</strong> <strong>Solr</strong> <strong>Reference</strong> <strong>Guide</strong> <strong>6.0</strong><br />

475

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!