That's a great idea. I don't know if we can generate compile-time resolvable links to the latest Reference Guide. But I could certainly do a comment section saying something like:
/* * This is a learning configuration. You may want to add: * version field for SolrCloud (<link> or Section name) * additional request handlers with custom parameters or components (<link>) * a lot of request processors are implicit, you can override them or configure them via request parameters (<link>) * Update Request Processors (<link>) */ So with three +1 and no -1, I've gone ahead and created SOLR-12603. I'll prototype this and report progress on the ticket. Regards, Alex. On 30 July 2018 at 13:32, Christine Poerschke (BLOOMBERG/ LONDON) <cpoersc...@bloomberg.net> wrote: > +1 to the idea of a super-minimal configset. > > Perhaps minimal comments could include carefully chosen pointers into the > relevant sections of the Solr Ref Guide so that the transition from "a few > lines of easily understood config" to "fully comprehensive reference manual" > is less daunting? > > Christine > > From: dev@lucene.apache.org At: 07/30/18 05:11:08 > To: dev@lucene.apache.org > Subject: Re: Solr proposal: adding super-minimal configset > > +1 > Feel free to add a modicum of comments to those configs. It is a *learning* > schema after all. > > On Sun, Jul 29, 2018 at 9:57 PM Erick Erickson <erickerick...@gmail.com> > wrote: >> >> +1 from my perspective. I remember the first time I looked at a Tomcat >> (?) config file a almost ran screaming out the door. What I >> particularly like about your bare-bones schema is that it shows how >> much is _unnecessary_ in the "kitchen sink" version. >> >> I strongly suspect that people are afraid to take anything out for >> fear that it'll break something else and this schema shows how little >> is absolutely necessary. >> >> Best, >> Erick >> >> >> On Sun, Jul 29, 2018 at 10:35 AM, Alexandre Rafalovitch >> <arafa...@gmail.com> wrote: >> > Hi, >> > >> > I would like to add a super-minimal learning-schema example to Solr as >> > one of the configsets. >> > >> > The current proposal is at: >> > >> > https://github.com/arafalov/solr-presentation-2018-may/tree/master/configs/initial >> > . It is 21 lines of managed-schema and 12 lines of solrconfig.xml. No >> > extra files. >> > >> > The associated presentation is at >> > >> > https://www.slideshare.net/arafalov/rapid-solr-schema-development-phone-directory >> > and is backed by the commit-by-commit versions of the >> > >> > https://github.com/arafalov/solr-presentation-2018-may/commits/master/configs/evolution >> > and the dataset, also in the repo. >> > >> > It is a learning schema, not SolrCloud ready, no caches configured, no >> > parent/child, no unused fieldType definitions and uses >> > SortableTextField and dynamicField * to achieve quickest learning >> > start and flexibility. This is based on my strong opinion that the >> > kitchen-sink approach we currently have make any specific features >> > invisible in those 969/1366 lines +extraFiles. >> > >> > I am looking for other committers' +1/-1 on this idea. I am happy to >> > do some modifications if they are deemed absolutely necessary. >> > >> > A dataset would have been nice to include as well, but the one I have >> > is GPLv3 or Creative Commons (Share Alike 3.0) - not sure if Share >> > Alike is an issue. >> > >> > Regards, >> > Alex. >> > >> > --------------------------------------------------------------------- >> > 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 >> > -- > Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker > LinkedIn: http://linkedin.com/in/davidwsmiley | Book: > http://www.solrenterprisesearchserver.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
