sabi0 commented on issue #12501:
URL: https://github.com/apache/lucene/issues/12501#issuecomment-1675193472

   > > Besides having two implementations ... with the same "Lucene84" name 
will likely result in a lookup error?
   > Exactly and because of that its final.
   
   I just do not understand then how your suggestion to "subclass default 
codec. By that it keeps its name and code reading the index will look it up" 
would work?
   Having the "official" Lucene95Codec and MyCustomCodec sharing the same 
"Lucene95" name will result in lookup error, won't it?
   
   So I have to give my custom codec a new name. And then "plug" it in using 
some configuration property, I suppose?
   Or find a way to ensure "my" `META-INF/services` appears on the classpath 
before lucene-core.jar


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to