[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088184#comment-14088184
]
Mark Miller commented on SOLR-3619:
-----------------------------------
bq. how enabling an optional feature makes it hard to go to production?
Right now you basically start with how we recommend you go to production. From
what I understand, your proposal means everything just works as "schemaless"
and you would have to dig to figure out how to get out of this mode. Fine some
other config files to plug in, I don't know. By enabling this optional feature,
you are making the non optional part more difficult to get to and likely just
out of mind entirely.
bq. For those who want to lock down their schema, it should be easily
doable/changeable via an API.
If I though that was easier that it seems to me, I might be willing to go
further down that thought path.
[~hossman_luc...@fucit.org], any chance I can ask for your opinion on this
issue?
> 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
