On 2/6/23 02:40, Tomasz Elendt wrote:
Normally I would use Configset API but it doesn't allow to use <lib> directives without enabling authentication and this is not something I want to deal with :)
I think using <lib> directives is a way to get yourself into trouble. Better to add any extra jars to ${solr.solr.home}/lib or use the modules feature in 9.x. That way those jars get loaded exactly ONCE and are available to all cores. The biggest problem with <lib> is that if multiple cores use it for the same jars, Solr will load those jars more than once. In addition to wasting memory, some jars break when loaded more than once. It is very common for a solr instance to handle multiple cores, whether it's cloud or not.
I just double-checked something. You can create custom modules in the solr modules directory and add them to the SOLR_MODULES variable in solr.in.sh (typically /etc/default/solr.in.sh), or solr.in.cmd if you're willing to run Solr on Windows.
For docker installs, I think most people will have the solr home in a volume mounted inside the container, so it's pretty easy to just create a lib directory there and add jars.
Thanks, Shawn
