[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14067794#comment-14067794
]
Mark Miller commented on SOLR-3619:
-----------------------------------
It would be just like it is now. People don't start from scratch, they pull the
so called example config and build from that. You should be able to say, create
me a collection and get that at a minimum. Except it should be better - schema
guessing option, dynamic field option, production schema option, etc. Less
example, and more practical. It's all common sense, and it's basically how
things have worked anyway, it's just that automating it and simplifying it
hasn't happened yet. When I was at Lucid we did a lot of this with config
'templates' for their enterprise search product. You can get a default starting
template, a built in template, a user supplied template. Probably lot's of ways
to hide the current exposed complexity and not sacrifice power or control. We
should discuss all this in other issues though. This issue won't remove
collection1.
> 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
