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

Karthick Sankarachary updated LUCENE-2433:
------------------------------------------

    Attachment: LUCENE-2433.patch

> A Remoting Split Policy For Managing Multiple Remote Directories 
> -----------------------------------------------------------------
>
>                 Key: LUCENE-2433
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2433
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: contrib/*, Index
>    Affects Versions: 3.0.1
>            Reporter: Karthick Sankarachary
>         Attachments: LUCENE-2433.patch
>
>
> (Please note that the feature described in LUCENE-2425 is required reading 
> for this issue.) 
> The remoting split policy is an abstraction for a split index, where each 
> sub-index points to a (potentially remote) URI-based directory. More 
> formally, it establishes mappings between URIs and directories using the 
> concept of a URIDirectory. Basically, that interface allows one to construct 
> a directory instance based on a URI value. 
> Currently, the following two URIs have been mapped:
> a) File URI: In this case, the path specified in the file URI maps to the 
> location of a FSDirectory. While the path usually points to a folder in the 
> local file system, it may refer to a NFS mount point, in which case the 
> sub-directory is not co-located with the super-directory of the split index.
> b) RAM URI: In this case, the path specified in the URI may be empty, in 
> which case a volatile RAMDirectory is created. In the event the path is 
> non-empty, the RAM-based directory acts as a facade for a file-system-based 
> directory.
> More (industrial-strength) URI mappings are currently in the works, and will 
> be added as they become available.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to