[
https://issues.apache.org/jira/browse/SOLR-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980548#comment-13980548
]
Yonik Seeley edited comment on SOLR-4478 at 4/25/14 1:08 AM:
-------------------------------------------------------------
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...
{code}
/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"?>
<response>
<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
name="code">400</int></lst>
</response>
/heliosearch/solr/example$ find solr -name solrconfig.xml
solr/collection1/conf/solrconfig.xml
solr/configsets/generic/conf/solrconfig.xml
/heliosearch/solr/example$ cat solr/books/core.properties
#Written by CorePropertiesLocator
#Thu Apr 24 20:23:51 EDT 2014
name=books
{code}
So, it's interesting that the written core.properties 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 correctly.
was (Author: [email protected]):
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...
{code}
/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"?>
<response>
<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
name="code">400</int></lst>
</response>
/heliosearch/solr/example$ cat solr/books/core.properties
#Written by CorePropertiesLocator
#Thu Apr 24 20:23:51 EDT 2014
name=books
{code}
So, it's interesting that the written core.properties 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 correctly.
> Allow cores to specify a named config set in non-SolrCloud mode
> ---------------------------------------------------------------
>
> Key: SOLR-4478
> URL: https://issues.apache.org/jira/browse/SOLR-4478
> 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 core.properties 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
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
