You can persist the IndexConfiguration somewhere using a Serializable object and persisting the configuration on a "File using an ObjectOutputStream", persist the configuration on a "persistent mechanism like a Database or on a fever of the moment a JSON storage" or like "Solr" using a Xml File.
I don't realize any other alternative at moment. The Index Configuration indeed is the most simple configuration in Lucene, you don't have too much parameters to worry about as you mention, major issue is that the Index can store multiple documents configurations and since the search is applied over fields on Documents, major gap is "which Document set was used on an Index". Regards. On Tue, Apr 22, 2014 at 2:48 AM, Ramprakash Ramamoorthy < youngestachie...@gmail.com> wrote: > Group, > > We are creating indexes (say 3) with different writer config details (merge > policy, codec & other config details vary for those 3 indexes), add some > documents & close all of them during application shutdown. > > We have to reopen them and add more documents during application restart. > But this requires the previous IndexWriterConfig settings for opening those > indexes in APPEND mode which is tedious as we need to map those indexes to > config parameters. Is there any other way to get the already available > config parameters from the IndexWriter? > > Thanks in advance. > > -- > With Thanks and Regards, > Ramprakash Ramamoorthy, > Chennai. >
