[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Potter updated SOLR-3619:
---------------------------------
Attachment: SOLR-3619.patch
Here is a patch that introduces a *server* directory.
First, note that many of the files that were in the example will be svn mv'd to
preserve history when I do the commit, but I've included them as "adds" using
{{svn diff --show-copies-as-adds}} so that you can actually try out this patch
if you're so inclined.
The new directory structure of packaged Solr will be:
{code}
<tip>
|__bin (see SOLR-3617 for scripts)
|__solr (for *nix)
|__solr.cmd (for Windows)
|__contrib
|__dist
|__docs
|__example
|__example-DIH
|__example-schemaless
|__exampledocs
|__multicore
|__solr
|__licenses
|__server
|__contexts
|__etc
|__lib
|__logs
|__resources
|__scripts
|__solr
|__solr-webapp
|__start.jar
|__webapps
{code}
I left the examples untouched as much as made sense; basically the example
directory just contains solr home directories for our existing examples. In
other words, example now contains examples and server contains scripts,
binaries, and resources needed to run Solr as a server or any of the examples.
I've run ant precommit (with clean-jars and jar-checksums) and ant package and
the build changes seem to work. There's probably still some clean-up needed for
the README.txt files but I took a stab and updating those as well.
*The biggest thing we now need to decide is what a default config looks like?*
Once you start Solr with the new scripts and server directory, there is no core
or collection created (ie. no more collection1). So if a user wants to create a
new core, they need some config to point at.
I vote for a minimal solrconfig.xml and managed-schema; basically I would strip
out all non-essential elements from the solrconfig.xml from the schema-less
example for Solr's default config.
Also, to be clear, a user can launch any of the examples if they are so
inclined using:
bin/solr -e <EXAMPLE> (see SOLR-3617)
for instance
bin/solr -e dih
will launch Solr from the server directory with solr.solr.home set to
example/example-DIH/solr
I'm asking if we want to include a minimal solrconfig.xml / schema.xml
configuration that new users can use to setup their own index? If so, where
should that live? I think server/solr/default_conf makes sense but am not
married to that path. Perhaps we could use XSL transform to strip out
non-essentials from the solrconfig.xml in example-schemaless?
> 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: [email protected]
For additional commands, e-mail: [email protected]
