AndreyBozhko commented on issue #13101: URL: https://github.com/apache/lucene/issues/13101#issuecomment-1945225900
Thanks for taking a look @uschindler - I have to admit that I didn't fully grasp your comment about having a separate Lucene per core. My original understanding was that for the example I described, the loading and reloading of SPI occurs during the Solr node (and not core) startup. So very early in Solr node's lifecycle, it would load all Lucene classes (makes total sense that these are per-node), and also load other libraries (user-provided plugins) shared at the node level. But even if we only deal with shared classes, users can still encounter a `ClassNotFoundException` similar to the example above. @HoustonPutman Please correct me if there's something that I misinterpreted about the issue from our initial discussion. -- 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: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
