The benefit is to update directly on the zookeeper and no need to touch the file system.
And functional aspects is what I wrote in my first email, I want to change the default boost values for specific request handlers and I don't want to pass them via the Solr API. Because we have our own REST API which will internally translated into Solr's API and in the process we read lot of configs from solrconfig.xml Thanks & Regards, Kranti K Parisa http://www.linkedin.com/in/krantiparisa On Thu, Sep 12, 2013 at 3:14 PM, Upayavira <u...@odoko.co.uk> wrote: > ** > Question is, what do you want to achieve? What benefit do you see yourself > getting from having configs in zookeeper? > > There may be another way of getting those benefits. > > Also note, whilst you can upload solrconfig.xml to Zookeeper as a part of > SolrCloud, you still need to reload a core to make the changes take effect. > Which is much the same as changing the file on disk and reloading the core > in a non-SolrCloud setup. So not sure what the benefit might be that you're > after. > > Upayavira > > On Thu, Sep 12, 2013, at 06:54 PM, Kranti Parisa wrote: > > Cool, thanks for the info. I am not using SolrCloud yet, but have plans > and this would be another motivation factor. > > Thanks & Regards, > Kranti K Parisa > http://www.linkedin.com/in/krantiparisa > > > > On Thu, Sep 12, 2013 at 1:20 PM, Shawn Heisey <s...@elyograg.org> wrote: > > On 9/12/2013 11:02 AM, Kranti Parisa wrote: > > As Solr 4.5 allows to store solr.xml in zookeeper, any ideas for > > supporting the same for other config files especially solrconfig.xml? so > > that we can change the relevance (boosting/scoring) settings, like qf, > > bf etc, for different request handlers on the fly? > > Using Zookeeper means that you are using SolrCloud. SolrCloud has kept > all core-level configuration (solrconfig.xml, schema.xml, etc) in > zookeeper since before its public debut with version 4.0. It already > does exactly what you are asking. > > I think that eventually Solr will move to a point where zookeeper will > be required, and basically there will be no "SolrCloud" distinction - if > you're running Solr at all, then you're running SolrCloud. Assuming > that I'm right about that, I don't know if it will happen with 5.0 or > 6.0. There's a lot of life left in Solr 4.x. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > > > > >
