That's really the point of the default managed-schema, to be a base you use for your customizations. In fact, I often _remove_ most of the fields (and especially fieldTypes) that I don't need. This includes dynamic fields, copyFields and the like.
Sometimes it's actually easier, though, to just start all over. BTW, do not delete any field that begins and ends with an underscore, e.g. _version_ unless you know exactly what the consequences are.... Best, Erick On Wed, Feb 7, 2018 at 2:59 PM, Pratik Patel <pra...@semandex.net> wrote: > Hello all, > > I have added some fields to default managed-schema file. I was wondering if > it is safe to take default managed-schema file as is and add your own > fields to it in production. What is the best practice for this? As I > understand, it should be safe to use default schema as base if documents > that are going to be indexed in solr will only have newly defined fields in > it. In fact, it helps because the common field types are already defined in > default schema which can be re-used. I looked through the documentation but > couldn't find the answer and more clarity on this would be helpful. > > Is it safe to use default managed-schema file as base add your own fields > to it? > > Thanks, > Pratik
