[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089854#comment-14089854
]
Timothy Potter commented on SOLR-3619:
--------------------------------------
Thanks Gregory and Hoss for contributing--I feel like a concrete plan is
starting to form!
bq. You start solr up the first time, you have 0 collections.
+1
Can we agree to start with 2 configsets (based on Hoss' plan above) and then
work on converting the other examples iteratively?
1) data_driven_schema_configs: field guessing and managed-schema
2) basic_configs: schema.xml (not managed) and no field guessing ... this
basically seems like the collection1 config we have today. So it seems like we
should just do: svn mv example/solr/collection1/conf and have
server/solr/configsets/basic_configs/conf
I also plan to enhance the start script (SOLR-3617) to have a command (new_core
or new_collection) that takes configset name as a parameter. The experience
would then be:
{code}
bin/solr start
bin/solr new_core -name gettingstarted -config data_driven_schema_configs
{code}
or
{code}
bin/solr start
bin/solr new_core -name prod_index -config basic_configs
{code}
Please let me know if there are anymore reservations about this approach as I'm
working on an updated patch based on this plan.
> 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, managed-schema,
> server-name-layout.png, solrconfig.xml
>
>
--
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
