On Mon, May 18, 2009 at 4:06 PM, KK <dioxide.softw...@gmail.com> wrote: > Do we have to extend the CoreAdminHandler class and use some methods therein > to register a new core? no. th create command will do that > Thanks in appreciation. > > --KK > > On Mon, May 18, 2009 at 12:48 PM, KK <dioxide.softw...@gmail.com> wrote: > >> Hi, >> What is the simplest way of registering a new solr core? Do we have to use >> some standard APIs for this, or making a Ajax get call to >> http://localhost:8983/solr/admin/cores >> >> with proper request parameter lik these, >> >> [?action=CREATE&name=coreX&instanceDir=path_to_instance_directory&config=config_file_name.xml&schema=schem_file_name.xml&dataDir=data] >> will do the job. I think this should work. Correct me if I'm wrong >> The process remains same for other requests as well[ like getting core >> status, reload, rename etc], right? >> >> Also, I would be thankful if someone can point me to some good tutorial on >> adding new cores to the existing ones, configuring multicore indexing etc. I >> don't find the solr wiki that useful for doing the same. >> >> >> Thanks, >> KK >> >> >> 2009/5/14 Noble Paul നോബിള് नोब्ळ् <noble.p...@corp.aol.com> >> >>> usually it happens fast . and the request returns only after the cor >>> creation is completed. So if you are doing all the operations in the >>> same thread no need to wait. >>> >>> >>> >>> >>> On Thu, May 14, 2009 at 7:37 PM, KK <dioxide.softw...@gmail.com> wrote: >>> > >>> > Thank you very much. LOL, Its in the same wiki I was told to go through. >>> > I've a question regarding creating ofsolr cores on the fly. The wiki >>> says, >>> > >>> > .....Creates a new core and register it. If persistence is enabled >>> > (persist=true), the configuration for this new core will be saved in >>> > 'solr.xml'. If a core with the same name exists, while the "new" created >>> > core is initializing, the "old" one will continue to accept requests. >>> Once >>> > it has finished, all new request will go to the "new" core, and the >>> "old" >>> > core will be unloaded..... >>> > >>> > So I've to wait for some time [say a couple of secs, may be less than >>> that] >>> > before I start adding pages to that core. I think this is the way to >>> handle >>> > it , otherwise some content which should have been indexed by the new >>> core, >>> > will get indexed by the existing core[as the wiki says], which I don't >>> want >>> > to happen. Any other ideas for handling the same. >>> > >>> > >>> > Thanks, >>> > KK. >>> > >>> > 2009/5/14 Noble Paul നോബിള് नोब्ळ् <noble.p...@corp.aol.com> >>> >> >>> >> Solr already supports this . >>> >> please refer this >>> >> >>> >> >>> http://wiki.apache.org/solr/CoreAdmin#head-7ca1b98a9df8b8ca0dcfbfc49940ed5ac98c4a08 >>> >> >>> >> ensure that your solr.xml is persistent >>> >> >>> >> >>> http://wiki.apache.org/solr/CoreAdmin#head-7508c24c6e2dadad2dfea39b2fba045062481da8 >>> >> >>> >> On Thu, May 14, 2009 at 3:43 PM, KK <dioxide.softw...@gmail.com> >>> wrote: >>> >> > Thank you very much. Got the point. >>> >> > One off the track question, can we automate the creation of new >>> cores[it >>> >> > requires manually editing the solr.xml file as I know, and what about >>> >> > the >>> >> > location of core index directory, do we need to point that manually >>> as >>> >> > well]. >>> >> > After going through the wiki what I found is we've to mention the >>> names >>> >> > of >>> >> > cores in solr.xml. I want to automate the process in such a way that >>> >> > when a >>> >> > user registers[ on say my site for the service], we'll create a >>> >> > coresponding >>> >> > core for the same user and with a specific core id[unique for this >>> user >>> >> > only] so that the user will be given a search interface that will >>> >> > redirect >>> >> > all searches for this user to http://host:port/<unique core name for >>> >> > this >>> >> > user>/select >>> >> > Will apprecite any ideas on this. >>> >> > >>> >> > Thanks, >>> >> > KK. >>> >> > >>> >> > 2009/5/14 Noble Paul നോബിള് नोब्ळ् <noble.p...@corp.aol.com> >>> >> > >>> >> >> there is no hard limit on the no:of cores. it is limited by your >>> >> >> system's ability to open files and the resources. >>> >> >> the queries are automatically sent to appropriate core if your url >>> is >>> >> >> >>> >> >> htt://host:port/<corename>/select >>> >> >> >>> >> >> On Thu, May 14, 2009 at 1:58 PM, KK <dioxide.softw...@gmail.com> >>> wrote: >>> >> >> > I want to know the maximum no of cores supported by Solr. 1000s or >>> >> >> > may be >>> >> >> > millions all under one solr instance ? >>> >> >> > Also I want to know how to redirect a particular query to a >>> >> >> > particular >>> >> >> core. >>> >> >> > Actually I'm querying solr from Ajax, so I think there must be >>> some >>> >> >> request >>> >> >> > parameter that says which core we want to query, right? Can some >>> one >>> >> >> > tell >>> >> >> me >>> >> >> > how to do this, any good pointers on the same will be helpful as >>> >> >> > well. >>> >> >> > Thank you. >>> >> >> > >>> >> >> > --kk >>> >> >> > >>> >> >> >>> >> >> >>> >> >> >>> >> >> -- >>> >> >> ----------------------------------------------------- >>> >> >> Noble Paul | Principal Engineer| AOL | http://aol.com >>> >> >> >>> >> > >>> >> >>> >> >>> >> >>> >> -- >>> >> ----------------------------------------------------- >>> >> Noble Paul | Principal Engineer| AOL | http://aol.com >>> > >>> > >>> >>> >>> >>> -- >>> ----------------------------------------------------- >>> Noble Paul | Principal Engineer| AOL | http://aol.com >>> >> >> >
-- ----------------------------------------------------- Noble Paul | Principal Engineer| AOL | http://aol.com
