A broad question - What could go wrong if I copy paste a live index and use as backup

I'm sorry for a vague question like this, but lemme narrow it down- I am trying to take back up of my live lucene index(Max size is 1-3 GBs). I am completely aware of the cleaner 'replicator' module, but I figured out it is too much code change for me. So here's what I am planning - I will copy

Re: A broad question - What could go wrong if I copy paste a live index and use as backup

I'm surprised that you say that you do not have problems with these types of errors, in some cases you could miss some files that are part of the last commit point, making the backup impossible to restore? Have you looked at PersistentSnapshotDeletionPolicy? Le mar. 17 avr. 2018 à 13:36,

Re: Error configuring Spell Checker

This mailing-list is for questions about using Lucene as a Java library. You might want to try the solr-user mailing-list instead. Le lun. 16 avr. 2018 à 19:25, genel a écrit : > We've been using SOLR for quite awhile. I'm attempting to install spell > checking. > > I think I

Help! - Max Segment name reached

We have an index that has run into this bug: https://issues.apache.org/jira/browse/LUCENE-7999 Although this is reported to be fixed in Lucene 7.2, we are at 4.10.4 and cannot upgrade. By looking at the code it seems that the last segment number counter is persisted in segment_h. When

RE: Help! - Max Segment name reached

Thanks, I will try that. Why haven't more people run into this issue? The next segment number is persisted, so if an index has a long life it should eventually run into this problem. Stuart M Goldberg Senior Vice President of Software Develpment FIX Flyer LLC http://www.FIXFlyer.com/ NOTICE TO

Re: Help! - Max Segment name reached

Hi, Create a new empty index in a new directory and use addIndex() using the other directory with the broken index. This will copy all segments but renumber them. Uwe Am April 17, 2018 3:52:27 PM UTC schrieb Stuart Goldberg : >We have an index that has run into this