I simply do not recommend going to production with schemaless. That mechanism must make certain assumptions about the data and simply cannot anticipate all the types of searching you need to do.
As Alessandro says, you can define whatever you want "by hand" and still have schemaless add input. It becomes a matter of preference, would you rather have documents with fields that haven't been seen before fail immediately? Or would you rather have them get new fields that you then have to discover? I prefer the former. Best, Erick On Fri, Jun 23, 2017 at 3:41 AM, alessandro.benedetti <a.benede...@sease.io> wrote: > Quoting the official solr documentation : > " You Can Still Be Explicit > Even if you want to use schemaless mode for most fields, you can still use > the Schema API to pre-emptively create some fields, with explicit types, > before you index documents that use them. > > Internally, the Schema API and the Schemaless Update Processors both use the > same Managed Schema functionality." > > Even using schemaless you can use the managed schema APi to define your own > field types and fields. > > For more info [1] > > [1] > https://lucene.apache.org/solr/guide/6_6/schemaless-mode.html#SchemalessMode-EnableManagedSchema > > > > ----- > --------------- > Alessandro Benedetti > Search Consultant, R&D Software Engineer, Director > Sease Ltd. - www.sease.io > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Query-Partial-Matching-on-auto-schema-tp4342502p4342509.html > Sent from the Solr - User mailing list archive at Nabble.com.
