[
https://issues.apache.org/jira/browse/SOLR-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14219428#comment-14219428
]
Alexandre Rafalovitch commented on SOLR-3619:
---------------------------------------------
bq. Using configsets in conjunction with schemaless mode (or even a config
where the schema API is active) seems like it might not be a good idea.
This actually raises another question. If I have, for example, REST-controlled
stop-list and have multiple collections share the configset in non-cloud mode,
would other collections even know that the set was updated?
bq. I'm not sure what to do about it, though.
Could we fix that by adding a *clone* parameter to *CREATE* call, if the
current behavior has to stay?
> 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: 5.0, Trunk
>
> Attachments: SOLR-3619.patch, SOLR-3619.patch, SOLR-3619.patch,
> managed-schema, server-name-layout.png, solrconfig.xml
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
