lucy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <>
Subject Re: [lucy-dev] Custom Backend for Index : Equivalent of (Lucene)
Date Thu, 15 Mar 2018 13:51:21 GMT

On 2018/03/15 13:11:16, Nick Wellnhofer <> wrote: 
> On 15/03/2018 00:14, wrote:
> > I want to save the index files in rocksdb. Idea is to use another opensource project
- (or other WAL reading mechanism) by which I can
replicate the index data to slave systems.
> I'm not sure whether such an approach makes sense. Lucy is basically a 
> specialized database itself, so your question is similar to asking how you 
> could replicate a MySQL database using a key-value store.
> > What will be equivalnet of in Apache lucy.  I see
> > I see FSDirHanlde.c and its corresponding files (FSFileHandle.c,FSFolder,FileHandle.c,Folder.c)
> > and RamDirHandle.c and its corresponding files.
> > 
> > Can some one please provides pointers if my approch is correct . Will it cause issues
in merging process.
> You can implement your own storage backend by subclassing Folder, FileHandle 
> and DirHandle. Lucy adheres to a write-once philosophy, so theoretically, it 
> should be possible to use a key-value DB as backend. But it's probably a lot 
> easier to move the index files to slave machines in more direct way.
> Also, what's your motivation for replicating Lucy indices? Availability? 
> Performance? Maybe there's a simpler overall approach.
> Nick

Hello ,
Thanks for the reply. its more about availability.
I went through this link -
I was thinking of implementing ; can you suggest what will be best method of implementing
above methodlogy

View raw message