+1 for nuking multi core example. And "schema less" should become the new default too, nuking yet another set of parallel configs!
-- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com 28. aug. 2013 kl. 16:47 skrev Mark Miller <[email protected]>: > I have an old JIRA where I started working on this, but I cannot find it. > > There has been no need for the multi core example for years now. I did a > bunch of work taking it out at one point, but I'm sure that work is old > enough to be useless now. Never go around to committing it. > > A few tests tie into those configs and I think there was some other flotsam > and jettsom to clean up. > > - Mark > > On Aug 27, 2013, at 6:10 PM, Erick Erickson <[email protected]> wrote: > >> bq: I think we should just get rid of it entirely >> >> +1, especially since we're going to core discovery, the collections API, etc. >> >> FWIW, >> Erick >> >> >> On Tue, Aug 27, 2013 at 3:42 PM, Shawn Heisey <[email protected]> wrote: >> On 8/27/2013 11:24 AM, Jack Krupansky wrote: >> I just happened to notice that the solr.xml file in the Solr >> example/multicore in branch_4x (and 4.4 as well) is still in the old >> legacy format (with <cores>/<core>). Is that merely an oversight or >> intentional for demonstrating backwards compatibility? >> >> The example/multicore directory seems to generally very out of date. The >> schema uses an ancient version, and doesn't have any good examples of how to >> use analyzers effectively. I'm fairly sure that all the examples use >> solr.xml and are therefore inherently multicore. >> >> Unless we plan to thoroughly update the multicore example so it's as modern >> as the main example, I think we should just get rid of it entirely. >> >> If we need an example that uses legacy config methods, I think we should >> make a new subdirectory. It should come with an extensive README and the >> solrconfig/schema should be more heavily commented than the standard example. >> >> Thanks, >> Shawn >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
