Rick: It'll be an uphill battle to change the configs I think.. That said there are no plans to go in that direction, but it's certainly a valid discussion to have.
I've seen a _lot_ of configs in the wild with weird indentation, they tend to get that way because there are lots of situations I've seen where people edit them through some kind of remote terminal and can only edit in some vi-like editor. Which may be customized a zillion different ways in terms of how indentation is handled. That's something that we'd need to be sensitive to when considering an indentation-sensitive format. Erick On Fri, Oct 7, 2016 at 9:50 AM, Rick Leir <rl...@leirtech.com> wrote: > Thanks for using the word bewildering, I agree. > > > While we are talking of simplifying solrconfig.xml, may I mention YAML? I > find the YAML format so much more readable than XML. > > > I have not looked at the code which reads the config, so I do not know how > big a change it is to use cfg4j and read in YAML. > > > Perhaps I should ask this on the dev list. And I hope I am not revisiting a > discussion which has already been decided. > > cheers -- Rick > > > On 2016-10-05 10:15 AM, Erick Erickson wrote: >> >> Charlie: >> >> I like that idea. It's bewildering how much stuff is in the config. I >> do think there's value in having it all there though since people >> won't even know to look in, say, "kitchen-sink-solrconfig.xml" for all >> the _other_ things that can be done.... >> >> Perhaps comment out all the "extra stuff" and move it to the end of >> the config files? >> >> And how many people have been tripped up by un-defining the "text" >> field in the schema and still having things break by the "df" field >> being set to text in solrconfig.xml? >> >> FWIW, >> Erick >> >> On Wed, Oct 5, 2016 at 1:29 AM, Charlie Hull <char...@flax.co.uk> wrote: >>> >>> On 05/10/2016 02:19, Walter Underwood wrote: >>>> >>>> I’m trying to bring up 6.2.1 after experience with 1.2 through 5.5, and >>>> it >>>> is a mess. >>>> I’ve done solid good practice (Zookeeper ensemble, chroot, data on EBS >>>> volume), >>>> but I’m stuck with a completely non-instructive stack trace. >>>> >>>> We run a separate data directory and SOLR_HOME, which is poorly >>>> supported >>>> by >>>> the startup script. I gave up and used a symlink to make it sorta happy. >>>> >>>> Still, I’m stuck with this. >>>> >>>> org.apache.solr.common.SolrException: Error processing the request. >>>> CoreContainer is either not initialized or shutting down. >>>> at >>>> >>>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:217) >>>> at >>>> >>>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:208) >>>> >>>> I’ve tried loading configs with bin/solr and with zkcli.sh. I get >>>> useless >>>> error messages >>>> from each of them. >>>> >>>> I worked on a commercial search product for ten years, and this wouldn’t >>>> pass basic QA. >>>> We need to do some work, people. >>> >>> >>> Last week I had to upgrade a proof-of-concept demo that ran on Solr 4 to >>> 6.2.1, using the Sunburnt client. I thought I'd use the Files example to >>> get >>> started. This wasn't exactly painless: I ended up having to disable >>> Managed >>> Schemas (I couldn't get Solr to use the old schema.xml), mess around with >>> Sunburnt (which assumed a certain URL structure to read schema.xml) and >>> generally chop large chunks out solrconfig.xml until it began to work. >>> >>> When we see clients with Solr issues the problems often stem from there >>> being *too much* in their configuration - they've started with one of the >>> example configs and added often conflicting settings, there's all kinds >>> of >>> irrelevant stuff hanging around (you probably don't need a Hungarian >>> stemmer >>> unless you're Hungarian), a zillion schema types you'll never need...I'm >>> beginning to wonder if an absolutely minimal Solr example configuration >>> might be a good idea. It's going to have to make assumptions (e.g. it's >>> probably going to assume English content) and it won't do anything >>> particularly clever, but I feel it might be a better place to start than >>> wondering what on earth all that commented-out XML does, especially the >>> bits >>> that say 'you probably shouldn't use this in production'. You can always >>> copy those bits back in later... >>> >>> I'll be in Boston next week if anyone wants to chat about this. Maybe >>> I'll >>> have a go at our Lucene Hackday on Tuesday (still some places free!) >>> >>> http://www.meetup.com/New-England-Search-Technologies-NEST-Group/events/233492535/ >>> >>> Cheers >>> >>> Charlie >>> >>> >>>> wunder >>>> Walter Underwood >>>> wun...@wunderwood.org >>>> http://observer.wunderwood.org/ (my blog) >>>> >>>> >>>>> On Oct 4, 2016, at 5:59 PM, Alexandre Rafalovitch <arafa...@gmail.com> >>>>> wrote: >>>>> >>>>> Hello, >>>>> >>>>> Three weeks ago I asked this list whether there was an interest in >>>>> running a virtual examples reading group, with "all questions >>>>> welcome". The response was sufficient to start planning the first >>>>> study group. >>>>> >>>>> The current projected date is start of November. You can register for >>>>> it at: https://www.surveymonkey.com/r/YLNVC27 (it is the same survey >>>>> as the first time - no need to do that again if you responded before). >>>>> The first run is free. >>>>> >>>>> Regards, >>>>> Alex. >>>>> >>>>> P.s. If you have Solr-using customers (e.g. you are running a Solr >>>>> cloud business), feel free to announce this to them and/or run your >>>>> own outreach and contact me directly with bulk emails of those >>>>> interested. >>>>> >>>>> P.p.s. I am also presenting on Solr examples at the Lucene/Solr >>>>> Revolution in about a week. If you have very strong opinions about >>>>> Solr examples, feel free to reach out directly and share them via >>>>> email or in person. The opinions do not have to be positive, though >>>>> having them constructive would be an nice. :-) >>>>> ---- >>>>> Newsletter and resources for Solr beginners and intermediates: >>>>> http://www.solr-start.com/ >>>> >>>> >>>> >>> >>> -- >>> Charlie Hull >>> Flax - Open Source Enterprise Search >>> >>> tel/fax: +44 (0)8700 118334 >>> mobile: +44 (0)7767 825828 >>> web: www.flax.co.uk > >
