alessandrobenedetti commented on PR #2809: URL: https://github.com/apache/solr/pull/2809#issuecomment-2508186617
> Is there a **non**-web-API way to configure a model? If not, why not? The vast majority of Solr's configuration is in solrconfig.xml, schema.xml, and some related config files linked from either, or in solr.xml for node level. Much of it can be manipulated with an API but nobody is forced to use such APIs to use the features, except for a few odd exceptions that I don't think we should emulate. Using an API is awkward for users that want to version-control their complete configuration and/or want to completely configure their Solr service in Docker, possibly overlayed with simple name-value apir config. We do all that where I work; no run-time manipulation post-deployment. Not even config in ZK (thanks to FileSystemConfigSetService). "Immutable Deployment" is the philosophy. Done everything except this bit, I agree that it takes an extra step to sopurce control this as you'll need to source control it and then push it to the model store (like it happens with Learning To Rank). I'm not sure it's a blocket though, I need to be cautious about the time I have left to work on this. Can't this be a future improvement? Contributed by others? -- 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...@solr.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
