Personally I'd like an XML formatter as part of the checkin process ;)... But that's not my point. In any "replace configs" discussion, we need to be aware of the many different environments that are out there "in the wild". An indentation-sensitive format like YAML brings with it its own problems. One of them is that if I don't have my editor set to use spaces I've introduced errors. At least with a format that has structure you can format it ugly without changing its meaning.
Best, Erick On Fri, Oct 7, 2016 at 4:45 PM, Rick Leir <rl...@leirtech.com> wrote: > > > On 2016-10-07 01:04 PM, Erick Erickson wrote: >> >> Rick: >> .. >> 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. > > I commonly do a diff of the xmls to see what has changed in a new release, > or what differs in an example. The indentation is often 'tidied up' in > different ways, making the diff almost useless. Perhaps I need to run an xml > formatter before doing any diff's on xml's. Also, perhaps the Solr > committers could agree to standardize on an xml formatter. > > Sorry for warping this thread so far: When you comment out a swatch of XML, > you need to allow for embedded comments. That is less troublesome with some > other flavours of config file. >> >> >> 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. >>> >>> >
