11.05.2016 Views

Apache Solr Reference Guide Covering Apache Solr 6.0

21SiXmO

21SiXmO

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Input<br />

Query Parameters<br />

Parameter Type Required Default Description<br />

core string Yes The name of one of the cores to be swapped.<br />

other string Yes The name of one of the cores to be swapped.<br />

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

asynchronously<br />

UNLOAD<br />

The UNLOAD action removes a core from <strong>Solr</strong>. Active requests will continue to be processed, but no new<br />

requests will be sent to the named core. If a core is registered under more than one name, only the given name<br />

is removed.<br />

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

The UNLOAD action requires a parameter ( core) identifying the core to be removed. If the persistent attribute of<br />

is set to true , the element with this name attribute will be removed from solr.xml.<br />

Unloading all cores in a <strong>Solr</strong>Cloud collection causes the removal of that collection's metadata from<br />

ZooKeeper.<br />

Input<br />

Query Parameters<br />

Parameter Type Required Default Description<br />

core string Yes The name of one of the cores to be removed.<br />

deleteIndex boolean No false If true, will remove the index when unloading the core.<br />

deleteDataDir boolean No false If true, removes the data directory and all sub-directories.<br />

deleteInstanceDir boolean No false If true, removes everything related to the core, including<br />

the index directory, configuration files and other related<br />

files.<br />

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

asynchronously<br />

MERGEINDEXES<br />

The MERGEINDEXES action merges one or more indexes to another index. The indexes must have completed<br />

commits, and should be locked against writes until the merge is complete or the resulting merged index may<br />

become corrupted. The target core index must already exist and have a compatible schema with the one or more<br />

indexes that will be merged to it. Another commit on the target core should also be performed after the merge is<br />

complete.<br />

http://localhost:8983/solr/admin/cores?action=MERGEINDEXES&core=new_core_name&i<br />

ndexDir=/solr_home/core1/data/index&indexDir=/solr_home/core2/data/index<br />

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

476

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

Saved successfully!

Ooh no, something went wrong!