I've fixed the problem below which was preventing SolrJ clients from making a call which would create a new core on a Solr server. I've also overloaded the createCore() method to allow the user to provide a config file and schema file if they desire (optional).
Here is what the changed code looks like: http://pastie.org/298579 There were very few changes in there, so it should be straight-forward. If there is a better or more organized way to get these changes into the SolrJ code, please let me know. The bugfix at least seems to be pretty essential. Thanks, - SinistralEnigma SinistralEnigma wrote: > > I can verify that I have the same problem when trying to use SolrJ's > CoreAdminRequest.createCore() to create a new core. It looks like this is > caused by the request accidentally sending a "core" parameter for the > parameter that is supposed to be "name" > > For example, to create a core named "newCore" SolrJ sends a request like > this: > http://localhost:8983/solr/admin/cores?action=CREATE&core=newCore&instanceDir=newcoredirectory&wt=javabin&version=2.2 > When it should send a request like this: > http://localhost:8983/solr/admin/cores?action=CREATE&name=newCore&instanceDir=newcoredirectory&wt=javabin&version=2.2 > > Also, not to be nit-picky, but it'd be nice to be able to send in the > config and schema parameters to the CoreAdminRequest.createCore() method. > - SinistralEnigma > > > Parisa wrote: >> >> Creating new Core By solrj API (CoreAdminRequest.createCore) fails >> because it doesn't set name parameter >> in getParameters method of CoreAdminRequest class >> >> >> solr version :1.3 >> >> Parisa >> > > -- View this message in context: http://www.nabble.com/Create-new-core-by-solrj-API-fails-tp19740822p20122717.html Sent from the Solr - Dev mailing list archive at Nabble.com.
