OK - now got trunk + solr-350.patch running nicely.
(There has been a small change to SolrResourceLoader.java since patch
creation - I can post an updated patch for review if I make any successful
changes.)
Out of the methods defined in MultiCoreAction, not all are implemented:
STATUS - works nice
LOAD - not implemented
UNLOAD - not implemented
RELOAD - works nice
CREATE - works nice
DROP - not implemented
PERSIST - works nice
SWAP - works nice
Are these all still required?
There is definitely a need for UNLOAD and/or DROP. Is there a conceptual
difference in mind between the 2?
I think UNLOAD just requires:
case UNLOAD: {
manager.remove(core.getName());
do_persist = true;
break;
}
With CREATE working, is there a need for LOAD?
Andy
>
> Andy,
> The code in the trunk is not the latest-greatest functionality wise, it
> reflects what we believe is stable enough to be made globally available -
> ie, a strong commitment that the APIs & functionality will not change; to
> get the latest level of functionality, the current development state, you
> still need to grab solr-350.patch
> (http://issues.apache.org/jira/secure/attachment/12374625/solr-350.patch)
> and apply it to the latest source trunk.
> Only when everything is agreed upon will the solr-350 code be merged in
> the
> trunk and the issue solved.
> Henri
> --
> View this message in context:
> http://www.nabble.com/Multicore---Unload---Reload-tp15429182p15433433.html
> Sent from the Solr - Dev mailing list archive at Nabble.com.
>
>
