[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088141#comment-14088141
]
Yonik Seeley commented on SOLR-3619:
------------------------------------
bq. I guess I was optimizing for a quick and easy getting started experience.
Solr doesn't have a getting to production problem,
+1
bq. I'm -1 on making a sensible default hard and a prototyping default easy.
They both need to be just as easy,
[...] bq. That is why we need both modes and it need to be just as easy to
choose either.
Having modes (esp called production vs prototyping) ups the perceived
complexity again and makes the prototyping mode feel cheap somehow (i.e. it's
just for show).
Schemaless can *sometimes* be desired in production (an internal cloud type
scenario where new collections are being created often by new users). For
those who want to lock down their schema, it should be easily doable/changeable
via an API. Same goes for the managed schema.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
