Rachid is exactly right. There's a long story here, I had the bright idea of editing the schema directly from the admin UI and one of the folks who, you know, understands browsers did the heavy lifting.... and then we were alerted to the fact that this is a huge security issue (i.e. uploading arbitrary XML to a website) so had to pull it all out.
The managed schema API is a was to have front-ends that change the schema and config. Best, Erick On Fri, Jul 29, 2016 at 7:19 AM, Shawn Heisey <apa...@elyograg.org> wrote: > On 7/27/2016 12:37 PM, Rachid Bouacheria wrote: >> I know that there still is the option to use schema.xml by using the >> ClassicIndexSchemaFactory but I am curious to hear from y'all that use >> managed schema how you are doing it and if there are any downside, >> gotchas, or if all is just much better :-) > > You have two choices. > > * Switch to the classic schema and use a file named schema.xml. > > * Don't worry about it. > ** Keep the config as-is. > ** Use existing methods with a new filename. > ** Ignore the Schema API functionality entirely. > > There's nothing preventing you from just editing managed-schema. Yes, I > am aware that the first thing the example file says is "don't edit this > file" ... but if you are not using the Schema API, then you don't have > to worry about that. > > If you're extremely careful, you can combine Schema API usage and hand > edits ... but I wouldn't recommend doing that. > > Thanks, > Shawn >
