We (well, me and one of the UI guys) had the brilliant idea of editing the configs through the admin UI.
Turns out it wasn't all that brilliant given security issues, see Uwe Schindler's comments here: https://issues.apache.org/jira/browse/SOLR-5287 on November 30th. So before raising a JIRA you might want to review the objections there to see if they would apply. In those instances where you _are_ using SolrCloud, the bin/solr script can be used to move things back and forth, either on a directory or individual file basis. Try: bin/solr zk -help and you'll see this output plus lots of details. Usage: solr zk upconfig|downconfig -d <confdir> -n <configName> [-z zkHost] solr zk cp [-r] <src> <dest> [-z zkHost] solr zk rm [-r] <path> [-z zkHost] solr zk mv <src> <dest> [-z zkHost] solr zk ls [-r] <path> [-z zkHost] solr zk mkroot <path> [-z zkHost] Best, Erick On Fri, Jan 5, 2018 at 6:24 AM, André Widhani <an...@digicol.com> wrote: > Hi Shawn, > > thanks for confirming. > > I am not using Solr Cloud (I forgot to mention that), or at least not in > all instances where that particular piece of code would be used. > > I'll think about opening a Jira issue, or just doing it iteratively through > the API. > > Regards, > André > > > 2018-01-05 15:05 GMT+01:00 Shawn Heisey <apa...@elyograg.org>: > > > On 1/5/2018 6:51 AM, André Widhani wrote: > > > >> I know I can retrieve the entire schema using Schema API and I can also > >> use > >> it to manipulate the schema by adding fields etc. > >> > >> I don't see any way to post an entire schema file back to the Schema API > >> though ... this is what most REST APIs offer: You retrieve an object, > >> modify it and send back the entire object. > >> > >> I could of course loop through all items in the schema, delete them and > >> re-create ... this sounds more complicated than it should be. > >> > >> Is there anything I might have missed in the documentation? > >> > > > > I'm not aware of any way to do this with the Schema API. It is designed > > to make individual changes, not wholesale replacement, so that a user > > doesn't need to understand the full XML syntax for the schema - they can > > send JSON-formatted change requests that are easier to understand than > the > > entire schema. > > > > If you're running SolrCloud, then you can upload an entire schema file to > > zookeepeer and reload the collection, which can be done remotely. > > > > If Solr is not in cloud mode, then the only option is to replace the file > > on the filesystem and then reload the core(s). > > > > The feature you want would open up the possibility of uploading a bad > > schema in the same way that manual edits can. You're free to file an > > enhancement issue in Jira, though. > > > > Thanks, > > Shawn > > > > > > -- > André Widhani > Research & Development > > *Don’t miss our latest news! * > www.digicol.de/news > > Digital Collections Content Systems GmbH > Hindenburgstraße 49, 22297 Hamburg > > Tel: +49 40 23535-128 > Fax: +49 40 23535-180 > E-Mail: andre.widh...@digicol.de > Internet: www.digicol.de > HRB Hamburg 48373, Geschäftsführer: Jörn Olsen > > Haftungsbeschränkung: > Diese Nachricht enthält vertrauliche Informationen und ist ausschließlich > für den Adressaten bestimmt. Der Gebrauch durch Dritte ist verboten. Das > Unternehmen ist nicht verantwortlich für die ordnungsgemäße, vollständige > oder verzögerungsfreie Übertragung dieser Nachricht. >
