[ https://issues.apache.org/jira/browse/LUCENE-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Rutherglen updated LUCENE-1738: ------------------------------------- Summary: IndexWriter.addIndexes without syncing (was: Expand IndexWriter to allow for replicating segments in near realtime) Changed because we can use addIndexes for replication (hopefully) . > IndexWriter.addIndexes without syncing > -------------------------------------- > > Key: LUCENE-1738 > URL: https://issues.apache.org/jira/browse/LUCENE-1738 > Project: Lucene - Java > Issue Type: Improvement > Affects Versions: 2.4.1 > Reporter: Jason Rutherglen > Priority: Minor > Fix For: 3.1 > > Original Estimate: 168h > Remaining Estimate: 168h > > When LUCENE-1313 is completed, it would be good to have a way to > replicate segments from one IndexWriter to another. > * Callback on successful flush (maybe for other events as well?) > * Ability to access files for a segment (which would presumably > be read from the IW ramdir), then copy them to a temporary > serialized ramdir (or equivalent as ramdir uses extra space in > blocks, whereas we'll already know the size of the files before > we write them). > * On the receiving end, we may be able to use > addIndexesNoOptimize(Directory[]), however this would entail > each directory having an extraneous segment_N file for each > replicated update (so we may want another format). > * It will rely on having a new public version of SegmentInfo. -- 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: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org