[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088029#comment-14088029
]
Timothy Potter commented on SOLR-3619:
--------------------------------------
Just an update on where things sit with this one. I've committed bin/solr
scripts (SOLR-3617) that will work with this new layout (and the legacy example
layout).
Next patch will include a new default_conf directory cooked up in
server/solr/default_conf. It's a minimized solrconfig.xml with managed-schema
and field-guessing enabled.
Having a default conf directory raises the question of how to use it during
core creation? This is mainly for non-cloud mode since in cloud mode, you have
to upload a config directory to ZooKeeper before creating cores and we have
tools for that.
We can either
# have the bin/solr script implement a "new_core" command {{bin/solr new_core
-n foo}} that creates the instance directory and cp -r's the default_conf to
instanceDir/conf for the user and then just hits the Core API's CREATE
endpoint, or
# add the ability to create a core using the default configuration to the
CoreAdminHandler, i.e. the core creation logic uses some logic added to the
SolrResourceLoader to find the default config when solrconfig.xml is not found
Of the two approaches, I'm favoring the first because it's more like the cloud
experience (tooling puts the config in the right place), esp. since the Core
Admin API isn't usable for creating new cores without doing some work upfront
on the command-line (i.e. user has to go create the instanceDir first anyway).
The first approach also avoids the Solr code doing something subtle behind the
scenes that the user is not aware of; for instance if the user fat-fingered the
name of their conf directory (e.g. their instance dir contains cnf instead of
conf) or something silly like that, building logic into the CoreAdminHandler to
use default config would skip their config and use the default one vs. throwing
an error about not finding their conf. However I have a way of talking myself
into things that require less work :P
> Rename 'example' dir to 'server' and pull examples into an 'examples'
> directory
> -------------------------------------------------------------------------------
>
> Key: SOLR-3619
> URL: https://issues.apache.org/jira/browse/SOLR-3619
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Timothy Potter
> Fix For: 4.9, 5.0
>
> Attachments: SOLR-3619.patch, SOLR-3619.patch, server-name-layout.png
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
