Hi,
I'm not sure if it's the best option but you could use replication to
copy the index (http://wiki.apache.org/solr/SolrReplication). As long as
you core is configured as a master you can use the fetchindex command to
do a one-time replication from the new core (see the HTTP API section in
the wiki page).
Regards,
gwk
On 3/24/2010 5:31 PM, Steve Dupree wrote:
*Solr 1.4 Enterprise Search Server* recommends doing large updates on a copy
of the core, and then swapping it in for the main core. I tried following
these steps:
1. Create prep core:
http://localhost:8983/solr/admin/cores?action=CREATE&name=prep&instanceDir=main
2. Perform index update, then commit/optimize on prep core.
3. Swap main and prep core:
http://localhost:8983/solr/admin/cores?action=SWAP&core=main&other=prep
4. Unload prep core:
http://localhost:8983/solr/admin/cores?action=UNLOAD&core=prep
The problem I am having is, the core created in step 1 doesn't have any data
in it. If I am going to do a full index of everything and the kitchen sink,
that would be fine, but if I just want to update a (large) subset of the
documents - that's obviously not going to work.
(I could merge the cores, but part of what I'm trying to do is get rid of
any deleted documents without trying to make a list of them.)
Is there some flag to the CREATE action that I'm missing? The Solr Wiki page
for CoreAdmin<http://wiki.apache.org/solr/CoreAdmin> is a little sparse on
details.
Is this approach wrong? I found at least one message on this list that
stated that performing updates in a separate core on the same machine won't
help, given that they're both using the same CPU. Is that true?
thanks in advance
~stannius
