I just tested that and /update does not seem to honor the default core value (same 404 issue). Is that a bug?
Regards, Alex. Personal blog: http://blog.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Mon, Jan 21, 2013 at 1:35 PM, Shawn Heisey <s...@elyograg.org> wrote: > On 1/21/2013 11:27 AM, O. Olson wrote: > >> http://localhost:8983/solr/**update <http://localhost:8983/solr/update> >> >> and I got a 404 too. I then looked at >> /example-DIH/solr/solr/conf/**solrconfig.xml and it seems to have >> <requestHandler >> name="/update" class="solr.**UpdateRequestHandler" />. >> >> I am confused why I am getting a 404 if /update has a >> handler? >> > > You need to send the request to /solr/corename/update ... if you are using > the solr example, most likely the core is named "collection1" so the URL > would be /solr/collection1/update. > > There is a lot of information out there that has not been updated since > before multicore operation became the default in Solr examples. > > The example does have defaultCoreName defined, but I still see lots of > people that run into problems like this, so I suspect that it isn't always > honored. > > Thanks, > Shawn > >
