That makes it clear. Thanks a lot for your help.
Pratik
On Feb 7, 2018 10:33 PM, "Erick Erickson" wrote:
> It can pretty much be used as-is, _except_
>
> you'll find one or more entries in your request handlers like:
> _text_
>
> Change "_text_" to something in your schema, that's the defau
It can pretty much be used as-is, _except_
you'll find one or more entries in your request handlers like:
_text_
Change "_text_" to something in your schema, that's the default search
field if you don't field-qualify your search terms.
Note that if you take out, for instance, all of your non
Hey Eric, thanks for the clarification! What about solrConfig.xml file?
Sure, it should be customized to suit one's needs but can it be used as a
base or is it best to create one from scratch ?
Thanks,
Pratik
On Wed, Feb 7, 2018 at 5:29 PM, Erick Erickson
wrote:
> That's really the point of the
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 st
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
