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

David Smiley commented on SOLR-17646:
-------------------------------------

This issue isn't really about the blockcache, but I see it as a prerequisite.  
Albeit there's nothing stopping a bespoke DirectoryFactory from existing that 
directly plugs in the blockcache – that's what the HDFSDirectoryFactory did.  
If this issue here got done, I could imagine a follow-on... perhaps plugging 
the blockcache into DirectoryFactory in a configurable way such that it's 
layered on top with a simple boolean toggle.  No need for a DF subclass for a 
specific backing technology (e.g. S3) if NIO becomes the preferred way to 
expose that backing technology.

Any way, this isn't anywhere near the top of my interests in Solr at the moment 
TBH.

> DirectoryFactory should support any NIO FileSystemProvider
> ----------------------------------------------------------
>
>                 Key: SOLR-17646
>                 URL: https://issues.apache.org/jira/browse/SOLR-17646
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: David Smiley
>            Priority: Major
>
> Ideally, the DirectoryFactory should support any NIO FileSystemProvider 
> without assuming the local/default FileSystem.  There are a variety of 
> implementations out there, such as for cloud storage (S3, GCP, ...), 
> [HDFS|https://github.com/damiencarol/jsr203-hadoop], and even Zip (imagine a 
> read-only directory).  This means switching from String & File to Path, and 
> avoiding sneaky methods that assume the default FileSystem.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to