[ 
https://issues.apache.org/jira/browse/SOLR-14044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052545#comment-17052545
 ] 

ASF subversion and git services commented on SOLR-14044:
--------------------------------------------------------

Commit c8c216514af29d94d3f269d01f57e1c0f2421b69 in lucene-solr's branch 
refs/heads/jira/SOLR-13101 from Yonik Seeley
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=c8c2165 ]

SOLR-14044: Delete collection bug fix by changing sharedShardName to use the 
same blob delimiter (#1293)

* Change sharedShardName to use blob delimiter and fix test

* use assign in test


> Support shard/collection deletion in shared storage
> ---------------------------------------------------
>
>                 Key: SOLR-14044
>                 URL: https://issues.apache.org/jira/browse/SOLR-14044
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>            Reporter: Andy Vuong
>            Priority: Major
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> The Solr Cloud deletion APIs for collections and shards are not currently 
> supported by shared storage but are an essential functionality required by 
> the shared storage design. Deletion of objects from shared storage currently 
> only happens in the indexing path (on pushes) and after the index file 
> listings between the local solr process and external store have been resolved.
>  
> This task is to track supporting the delete shard/collection API commands and 
> its scope does not include cleaning up so called “orphaned” index files from 
> blob (i.e. files that are no longer referenced by any core.metadata file on 
> the external store). This will be designed/covered in another subtask.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to