No problem, created this.
https://issues.apache.org/jira/browse/SOLR-3401 and related to 2605.
On Mon, Apr 23, 2012 at 11:39 AM, Stefan Matheis
wrote:
> Jamie, right .. that makes sense. right now the core-admin will not work in
> singlecore-mode because we have no core-name there.
> https://i
Jamie, right .. that makes sense. right now the core-admin will not work in
singlecore-mode because we have no core-name there.
https://issues.apache.org/jira/browse/SOLR-2605 should fix this, afterwards we
can show the core-admin for every configuration. would you mind to open a
ticket for tha
So I believe I see the reason now. Basically in app.js we check to
see if there is more than 1 core deployed to decide if we show the
core admin or not. I am not sure this is intended or not, but I would
think this isn't what we want the default action to be. Shouldn't we
always show the core ad
AIL PROTECTED]>
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: Re: Solr Core Admin
:
: Ok just FYI solr replaces the file instead of editing. This means that the
: webserver needs permissions in the directory to delete and create the
: solr.xml file. Once I fixe
unsubscribe
> Date: Thu, 20 Nov 2008 08:29:20 -0800
> Subject: Solr Core Admin
> From: [EMAIL PROTECTED]
> To: solr-user@lucene.apache.org
>
> I am trying to use the api for the solr cores. Reload works great but when
> I try to UNLOAD I get a massive exception in IOException. It seems to
> un
Ok just FYI solr replaces the file instead of editing. This means that the
webserver needs permissions in the directory to delete and create the
solr.xml file. Once I fixed that it no longer gave IOException errors.
On 11/20/08 8:29 AM, "Jeff Newburn" <[EMAIL PROTECTED]> wrote:
> I am trying t
