Hi Mark,
If can support in future, I think it's great. It's a really useful feature.
For example, user can use to refresh with totally new core. User can build
index on one core. After build done, can swap old core and new core. Then
get totally new core for search.
Also can used in the backup. I
FYI swap is def not supported in SolrCloud right now - even though it may work,
it's not been thought about and there are no tests.
If you would like to see support, I'd add a JIRA issue along with any pertinent
info from this thread about what the behavior needs to be changed to.
- Mark
On Se
Hi Chris,
Thanks for your help. Today I tried again and try to figure out the reason.
1. set up an external zookeeper server.
2. change /opt/solr/apache-solr-4.0.0-BETA/example/solr/solr.xml persistent
to true. and run below command to upload config to zk. (renamed multicore
to solr, and need to
: Below is my solr.xml configuration, and already set persistent to true.
...
: Then publish 1 record to test1, and query. it's ok now.
Ok, first off -- please provide more details on how exactly you are
running Solr. Your initial email said...
>>> In Solr 3.6, core swap function works
Hi Hoss,
Thanks for your quick reply.
Below is my solr.xml configuration, and already set persistent to true.
For test1 and tets1-ondeck content, just copied from
example/solr/collection1
Then publish 1 record to test1, and query. it's ok now.
INFO: [test1] webapp=/solr path=/sel
: In Solr 3.6, core swap function works good. After switch to use Solr 4.0
: Beta, and found it doesn't work well.
can you elaborate on what exactly you mean by "doesn't work well" ? ..
what does your solr.xml file look like? what command did you run to do the
swap? what results did you get from
