How are we doing the feedback? On the list? On the page in comments? Before looking too hard at the links (will later): 1) If we are talking about solrconfig.xml - there are now general properties that apply to multiple update handlers at once. And multiple of them may do that in order of the file. 2) We are starting to use configsets more heavily - but the documentation is fairly light, including the fact that you don't necessarily want to mix a configset and dynamicschema (because then configset reflects aggregate auto-generated schema changes). As well as some sort of cross references between configsets and core.properties
Regards, Alex. Personal: http://www.outerthoughts.com/ and @arafalov Solr resources and newsletter: http://www.solr-start.com/ and @solrstart Solr popularizers community: https://www.linkedin.com/groups?gid=6713853 On 10 December 2014 at 17:49, Chris Hostetter <hoss...@fucit.org> wrote: > > There have been a lot of structural changes to what a solr release will look > like starting with 5.0, and how we intend/expect people to run Solr -- both > to try the example(s) and in a "production installation" > > With that in mind, i created a new meta-page in the ref guide to try and > track: > > 1) the "big" areas we need to make sure we cover related to installation > 2) an audit of all pages that are impacted to *any* degree by these changes > > https://cwiki.apache.org/confluence/display/solr/INTERNAL+-+5.0+Ref+Guide+Overhaul+Notes > > #1 is certainly important, and I hope folks who have been a lot more > involved with the new /server/ structure and getting rid of the war (*cough* > tim *cough* miller) can step in and help direct those aspects of > documentation. > > > But in this email i'd like to focus on #2 since it's going to involve a lot > of fiddling with a *lot* of different. > > This type of work is ripe for for parallelization and diving up among a lot > of people -- but only if there is a clear understanding of what types of > edits are needed and what sort of pattern/model those edits should follow. > > I've taken a stab at "fixing" 5 sample pages from the ref guide to try and > show what i had in mind. I've linked not only to those 5 pages but also the > specific edits (so it's hopefully easy to see what's going on) in a box > labeled "Hoss'ss Proof Of Concenpt for edits" ... > > https://cwiki.apache.org/confluence/display/solr/INTERNAL+-+5.0+Ref+Guide+Overhaul+Notes#INTERNAL-5.0RefGuideOverhaulNotes-Thingstoauditindepth... > > > ... I'd appreciate feedback from folks on whether you think this is the > right direction to head in before I (or anyone else) try to dive in and do a > bunch of cleanup. > > > > > -Hoss > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org