There seems to be some fracturing in the format of various Solr configs. Most of the config uses XML, but some new features in the last few years are using JSON, particularly where SolrCloud and Zookeeper are concerned. When notifications about SOLR-9557 came through, it revealed that there is a config file sitting next to solrconfig.xml named "params.json" that Solr will use. I wasn't aware of this until reading that issue.
This leads me to suggest something rather drastic for 7.0: Consolidate all configuration formats and agree to consistent format usage unless there is another major discussion and agreement to change formats. I did consider starting this discussion in Jira, but it's fairly major, so the dev list seemed like the right place to start. Comments from some new users have come my way along the lines of "XML is so 90's ... get with the times!" Image problems like that can be fatal to a software project, even if there's no technical problem. The likely winner in the format discussion is pure unmodified JSON, but I'm not going to make any assumptions. SOLR-8029 has some format discussions that may be relevant here. IMHO, in order to make the idea successful, Solr 7.0 will need to automatically convert most configs on startup from the old format to the new format without user intervention. If there's something that we find we can't convert automatically, that should result in a failure to start, with a helpful message so the user has some idea what they need to do. Thoughts? Is this too scary to contemplate? Should I open an umbrella issue in Jira to get the ball rolling? Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
