AndreyBozhko commented on issue #13101: URL: https://github.com/apache/lucene/issues/13101#issuecomment-1945226818
I do realize that the issue title may have sounded too prescriptive - I certainly didn't mean that. But I would definitely like to have a discussion on what path forward (if any) makes the most sense. I realize that the feedback may be along the lines of _"The behavior of Lucene's AnalysisSPILoader is set in stone, and Solr should just work around that"_. Or, as a hypothetical alternative, Lucene could expose a way to invalidate the SPI cache, and applications like Solr may choose to use that (having full control, but also full responsibility over what they're doing). Or perhaps there are other ways to go about this. What are your thoughts? -- 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
