[ckan-dev] Problems with manual install of solr
Michael Speth
spethm at landcareresearch.co.nz
Fri Mar 13 02:35:02 UTC 2015
Thank you Florian,
That was exactly the problem!!!! The url should be: solr_url = http://127.0.0.1:8983/solr/default
Thank you again!!!
Message: 6
Date: Fri, 13 Mar 2015 09:52:44 +0800
From: Florian May <florian.wendelin.mayer at gmail.com<mailto:florian.wendelin.mayer at gmail.com>>
To: CKAN Development Discussions <ckan-dev at lists.okfn.org<mailto:ckan-dev at lists.okfn.org>>
Subject: Re: [ckan-dev] Problems with manual install of solr
Message-ID:
<CAK6Sqm0VQr8HMYrgV_FTVOKwLydT7tPn8Gto+Q-CCvigSWLbCQ at mail.gmail.com<mailto:CAK6Sqm0VQr8HMYrgV_FTVOKwLydT7tPn8Gto%2BQ-CCvigSWLbCQ at mail.gmail.com>>
Content-Type: text/plain; charset="utf-8"
Good morning Michael,
my gut feeling is your solr_url could possibly be
http://127.0.0.1/solr/collection1
Here's how I got it to work with one SolR core for three CKAN instances:
(apologies for the repost)
https://github.com/opendata/CKAN-Multisite/issues/10
The write-up should give you a feeling for the relation between SolR cores,
solr_url (/solr/CORE_NAME) and the SolR admin frontends.
Another approach would be one SolR core per CKAN instance - we got away
with a single SolR core as two of the three CKAN instances are
unobtrusively small.
Cheers,
Florian
--
Michael Speth
DevOps Computer Engineer
Landcare Research Consultant
________________________________
Please consider the environment before printing this email
Warning: This electronic message together with any attachments is confidential. If you receive it in error: (i) you must not read, use, disclose, copy or retain it; (ii) please contact the sender immediately by reply email and then delete the emails.
The views expressed in this email may not be those of Landcare Research New Zealand Limited. http://www.landcareresearch.co.nz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20150313/1bbc0ed7/attachment-0003.html>
More information about the ckan-dev
mailing list