[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088402#comment-14088402
]
Gregory Chanan commented on SOLR-3619:
--------------------------------------
bq. Gregory Chanan, you did a lot with the managed schema mode recently. What
do you think about it becoming the primary Solr 'mode' in it's current state?
Interesting question. I don't have a philosophical objection to it, like I
would with schemaless. My main concerns are:
- I think SOLR-6249 would definitely need to be addressed, it's too
non-intuitive to use programatically at this point
- Cassandra gave a good overview of the other limitations of the API. Those
are less serious than SOLR-6249, because instead of something breaking, you
might just get stuck. I'd have some concern that the usual workflow would be:
try managed schema -> get stuck -> write the schema manually. This is a worse
experience IMO than just telling users to write the schema manually.
So I think I'd pass on making it the "default" for now.
> 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
