[ https://issues.apache.org/jira/browse/SOLR-16153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17521707#comment-17521707 ]
David Smiley commented on SOLR-16153: ------------------------------------- Yes; I definitely want to ensure that the Directory abstraction is consulted such that a custom Directory can do its magic to make the copy cheap where that is supported. Based on what I see for the shard split code, and this will use similar logic, this already happens. > Clone Collection > ---------------- > > Key: SOLR-16153 > URL: https://issues.apache.org/jira/browse/SOLR-16153 > Project: Solr > Issue Type: New Feature > Security Level: Public(Default Security Level. Issues are Public) > Components: SolrCloud > Reporter: David Smiley > Priority: Major > > It should be possible to "clone" a collection, and to do so cheaply. This > might be its own command or be an option of collection creation; either way, > it'd be great to support the vast majority of the same options of collection > creation. A cloned collection should be the same in every way (shard ranges, > collection properties, replicas types and counts, etc.) unless configured to > be different (e.g. specify a different configSet). Most importantly, a > cloned collection should have the same data, and this can be accomplished via > UNIX hard links (when supported) to the underlying files. This would make > clones cheap! A no-data option should be supported as well, useful when the > intended action is to re-index subsequently. -- This message was sent by Atlassian Jira (v8.20.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org