[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067787#comment-14067787
]
Alexandre Rafalovitch commented on SOLR-3619:
---------------------------------------------
Ok, so what does this mean on the practical level: **create mycollection**.
Especially for people who are still trying Solr as opposed to doing production
setup (two different distributions?).
The way ES handles it now is by basically baking in the templates and defaults
into the core jars. So, the first time you issue a URL against non-existing
collection, it's created and inherits all the defaults (ids, endpoints, default
types (including multilngual), etc).
Solr requires everything explicitly. And you cannot expect people to create a
schema.xml and solrconfig.xml from scratch to get their first collection to
work. So, **something** has to pre-exist. And that something should be easy to
run as step 3 (worst case 4).
If it's not a pre-built collection, then we need some sort of wizard to create
the directory structure. How do you see that? Maybe with global configsets or
something similar? I would love that, but I am not sure that starting to talk
about the wizards in this JIRA is any smarter than rebuilding the whole set of
examples.
> 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
> Fix For: 4.9, 5.0
>
> Attachments: 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
