lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-4478) Allow cores to specify a named config set in non-SolrCloud mode
Date Fri, 25 Apr 2014 00:33:19 GMT


Yonik Seeley commented on SOLR-4478:

Does anyone have a simple working example they could share?  I've been manually testing new
4.8 features and have been stumped by this feature so far...

/heliosearch/solr/example$ mkdir -p solr/configsets/generic/conf/
/heliosearch/solr/example$ cp -r solr/collection1/conf/* solr/configsets/generic/conf/
/heliosearch/solr/example$ curl 'http://localhost:8983/solr/admin/cores?action=CREATE&name=books&configset=generic'

<?xml version="1.0" encoding="UTF-8"?>
<lst name="responseHeader"><int name="status">400</int><int name="QTime">20</int></lst><lst
name="error"><str name="msg">Error CREATEing SolrCore 'books': Unable to create core:
books Caused by: Can't find resource 'solrconfig.xml' in classpath or '/heliosearch/solr/example/solr/books/conf'</str><int

/heliosearch/solr/example$ cat solr/books/ 
#Written by CorePropertiesLocator
#Thu Apr 24 20:23:51 EDT 2014

So, it's interesting that the written contains no reference to the configset.
Anyway, I haven't dug into any code as I assume I'm just not interpreting the existing documentation

> Allow cores to specify a named config set in non-SolrCloud mode
> ---------------------------------------------------------------
>                 Key: SOLR-4478
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.2, 5.0
>            Reporter: Erick Erickson
>            Assignee: Alan Woodward
>             Fix For: 4.8, 5.0
>         Attachments: SOLR-4478-take2.patch, SOLR-4478-take2.patch, SOLR-4478-take2.patch,
SOLR-4478-take2.patch, SOLR-4478.patch, SOLR-4478.patch, solr.log
> Part of moving forward to "the new way", after SOLR-4196 etc... I propose an additional
parameter specified on the <core> node in solr.xml or as a parameter in the "discovery"
mode file, call it configSet, where the value provided is a path to a directory,
either absolute or relative. Really, this is as though you copied the conf directory somewhere
to be used by more than one core.
> Straw-man: There will be a directory <solr_home>/configsets which will be the default.
If the configSet parameter is, say, "myconf", then I'd expect a directory named "myconf" to
exist in <solr_home>/configsets, which would look something like
> <solr_home>/configsets/myconf/schema.xml
>                               solrconfig.xml
>                               stopwords.txt
>                               velocity
>                               velocity/query.vm
> etc.
> If multiple cores used the same configSet, schema, solrconfig etc. would all be shared
(i.e. shareSchema="true" would be assumed). I don't see a good use-case for _not_ sharing
schemas, so I don't propose to allow this to be turned off. Hmmm, what if shareSchema is explicitly
set to false in the solr.xml or properties file? I'd guess it should be honored but maybe
log a warning?
> Mostly I'm putting this up for comments. I know that there are already thoughts about
how this all should work floating around, so before I start any work on this I thought I'd
at least get an idea of whether this is the way people are thinking about going.
> Configset can be either a relative or absolute path, if relative it's assumed to be relative
to <solr_home>.
> Thoughts?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message