On 27/9/16 8:59pm, Jamie Jackson wrote: > In 4, with a separate servlet container, I used externally-defined, > container-managed jndi data sources. However, I'm in the middle of an > upgrade to 5 (before moving on to 6), and I had to add the DIH lib to each > core's solrconfig.xml and add connection details to each core's DIH config > xml. See this: > https://cwiki.apache.org/confluence/display/solr/Uploading+Structured+Data+Store+Data+with+the+Data+Import+Handler
The changes to solrconfig.xml are fine since that comes along with the zookeeper configuration bundle (I have that in version control, deployed using a combination of Jenkins and saltstack). The problem is that we too used to have everything bundled nicely in a war file in Solr 4 and that's all been removed. A major step backward for the Solr project for no benefit I can understand. Standard tomcat deployment practices were simple enough. But I like the approach you point out with the DIH file. Not as good as JNDI, but at least it gives us a place outside the Solr install where we can put DB connection details. Thanks for that. Ari -- --------------------------> Aristedes Maniatis GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
