You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would probably be nice to add via riak-admin updates on a per index-level and/or via API calls, gossiping the changes to other nodes (similar to how search_index/core creation works and can be included in the creation/update process). Of note, http://stackoverflow.com/a/23786869, look at RELOAD and how to expose that property due to restart constraints on the cores.
The text was updated successfully, but these errors were encountered:
Basho-JIRA
changed the title
Expose (and make simpler) configuration of certain solrconfig.xml fields per index-level
Expose (and make simpler) configuration of certain solrconfig.xml fields per index-level [JIRA: RIAK-2077]
Aug 9, 2015
So, I'm pretty new to this subject, but I can already point some problems:
As I write a lot, SolR commits tends to happen a lot. A SolR expert friend of mine explained me that any SolR commit invalidate cache (fq queries). I'd like to be able to tweak the commit interval to something that fit my needs, in order to get some advantages of solr cache. He explained me that autowarm is a way to mitigate that, yet we need to be able to set this easily.
SolrConfig.xml comments on this matter explain that high autoCommit value put risk because of AAE. Well, in my case AAE come second to SolR cache.
I need to use a component (namely Suggester), that requires a block of configuration inside the SolrConfig.xml. That's pretty simple, yet it requires the index to be created first, solrConfig.xml to be updated, and then solr to be reloaded.
In order to achieve this kind of tuning, i'd suggest Yokozuna to use XML inclusion through Xinclude or Entity Include to distinguish factory settings from custom extra configuration.
as per #358 (comment)
and other discussions we've had since, internally, w/ @fadushin @jonmeredith.
This would probably be nice to add via riak-admin updates on a per index-level and/or via API calls, gossiping the changes to other nodes (similar to how search_index/core creation works and can be included in the creation/update process). Of note, http://stackoverflow.com/a/23786869, look at RELOAD and how to expose that property due to restart constraints on the cores.
The text was updated successfully, but these errors were encountered: