[ 
https://issues.apache.org/jira/browse/SOLR-17671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bruno Roustant resolved SOLR-17671.
-----------------------------------
    Fix Version/s: 9.9
       Resolution: Fixed

> Replication and Backup should use an unwrapped Directory when copying files.
> ----------------------------------------------------------------------------
>
>                 Key: SOLR-17671
>                 URL: https://issues.apache.org/jira/browse/SOLR-17671
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Bruno Roustant
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 9.9
>
>          Time Spent: 4h 10m
>  Remaining Estimate: 0h
>
> Currently Replication and Backup copy files using a Directory created with 
> the configured DirectoryFactory. This Directory may be a FilterDirectory that 
> adds additional logic (e.g. encryption) that should not run when copying 
> files (e.g. do not decrypt).
> The proposal is to add a new REPLICATE value in the 
> DirectoryFactory.DirContext that would be used by replication and a new 
> BACKUP for backup to get the Directory to use. The DirectoryFactory would 
> unwrap the Directory in this case.
> One could expect that only one REPLICATE could be enough, but backup requires 
> more inner checksum verifications that may need to differentiate the logic 
> between the two (this is the case for encryption).
> Example:
> In the solr-sandbox encryption module, we would need a way to unwrap the 
> Directory used to copy files during index fetching. Otherwise the files are 
> decrypted by the EncryptionDirectory seamlessly during the files copy, ending 
> up with follower replicas having cleartext index.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to