[
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's an updated patch that I think is very close to being committable. Here
are the key changes in this patch:
1) Directory structure:
{code}
<tip>
|__bin
|__solr (for *nix)
|__solr.cmd (for Windows)
|__contrib
|__dist
|__docs
|__example
|__example-DIH
|__exampledocs
|__licenses
|__server
|__contexts
|__etc
|__lib
|__logs
|__resources
|__scripts
|__solr
|__configsets
|__basic_configs
|__data_driven_schema_configs
|__sample_techproducts_configs
|__solr-webapp
|__start.jar
|__webapps
{code}
The important part here is that I've moved some of the configurations from
under the example directory to be configsets under {{server/solr/configsets}}.
Specifically, {{example/example-schemaless/solr/collection1/conf}} becomes
{{server/solr/configsets/data_driven_schema_configs/conf}} and
{{example/solr/collection1/conf}} becomes
{{server/solr/configsets/sample_techproducts_configs/conf}} (I used Hoss'
suggested names)
2) When you start Solr using (bin/solr start), the server starts up with
{{server/solr}} as the solr.solr.home and no collections / cores are created. A
nice next step might be to {{bin/solr create_core}} if in standalone server
mode or {{bin/solr create_collection}} if in SolrCloud mode. I know we talked
about making cloud-mode the default start mode, which we can handle in another
ticket. For now, to get started, you can do:
{code}
bin/solr start
bin/solr create_core -n test
{code}
or
{code}
bin/solr start -cloud
bin/solr create_collection -n test
{code}
3) To run the examples, you can still use the bin/solr script, such as:
{{bin/solr -e schemaless}} will boot up Solr in standalone mode and then create
a new core named schemaless using the data_driven_schema_configs configset.
{{bin/solr -e techproducts}} will boot up Solr and then create a new core named
techproducts using the sample_techproducts_configs configset and then calls
post.jar to index {{example/exampledocs/*.xml}}
4) I took a stab and what the basic_configs should include but am not beholden
to what I have there now. I definitely would like some other eyes on this. I
know [~arafalov] has done a lot of nice work in this area, so please take a
close look at {{server/solr/configsets/basic_configs}}.
5) I left the dih example alone because it is more involved than just a
configset. Also, it seemed like we didn't need multicore anymore, so I deleted
that.
Overall, I think this is a more intuitive layout and much of the ease-of-use
comes from the bin/solr script doing most of the work for the user. Please give
this a good look and help me get it committed soon.
> 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, Trunk
>
> Attachments: SOLR-3619.patch, SOLR-3619.patch, SOLR-3619.patch,
> managed-schema, server-name-layout.png, solrconfig.xml
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
