[
https://issues.apache.org/jira/browse/SOLR-5756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621500#comment-14621500
]
Scott Blum commented on SOLR-5756:
----------------------------------
That sounds great. I will get on this in the next couple days. One clarifying
questions:
Suppose on read/reload, data exists in both the collection's `state.json` and
the shared `clusterstate.json` on load, which one should it prefer, and it
should any corrective action happen to de-dup? I would presume that it should
prefer `state.json` (and eagerly remove the entry from `clusterstate.json`?) in
this case, since it indicates someone successfully wrote out the new one but
failed to delete the old one.
> A utility API to move collections from internal to external
> -----------------------------------------------------------
>
> Key: SOLR-5756
> URL: https://issues.apache.org/jira/browse/SOLR-5756
> Project: Solr
> Issue Type: Bug
> Reporter: Noble Paul
> Assignee: Noble Paul
>
> SOLR-5473 allows creation of collection with state stored outside of
> clusterstate.json. We would need an API to move existing 'internal'
> collections outside
--
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
