Not quite sure what you mean, lucene needs some way to load a codec, and give parts of an index written with different codecs it would need tonload and select the right code at the right time.
Consider, for example the upgrade path. Let's say you have segments written with code 5.x and we in place upgrade to 6.x, lucene is going to need to know how to load up the codec for 5.x and 6.x. On Thu, Aug 4, 2016, at 09:03 AM, Aravinth T wrote: > I understand that, my question is different why we are loading it with > SPI, > > why we explicitly controlling the loading of Codecs > > > > > ---- On Thu, 04 Aug 2016 20:39:46 +0530 Greg Bowyer > <gbow...@fastmail.co.uk>wrote ---- > > > > > Codecs are loaded with the java service loader interface. That file is > > the hook used to tell the service loader that this jar implements Codec. > > > > Lucene internally calls service loader and asks what codecs are there. > > > > On Wed, Aug 3, 2016, at 11:23 PM, aravinth thangasami wrote: > > > I don't understand why we need to add custom codec name in this file > > > > > > Thanks & Regards > > > Aravinth > > > > > > On Thu, Aug 4, 2016 at 11:52 AM, aravinth thangasami < > > > aravinththangas...@gmail.com> wrote: > > > > > > > Hi all, > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > > For additional commands, e-mail: java-user-h...@lucene.apache.org > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org