Also, if you _know_ certain fields should be defined you can define them explicitly and let schemaless figure out all the others.
That said, eventually you're going to have to control your schema, schemaless is _not_ recommended for production systems unless you can absolutely guarantee the input is in a specific format. And by "specific format" I mean no field first encountered as, say, an int later comes through as a float. All date fields are of acceptable formats, no field first encountered as a single valued field is every multivalued later etc. And if you can guarantee that you can create an explicitly defined schema anyway. Best, Erick On Thu, Oct 19, 2017 at 2:00 AM, Emir Arnautović <emir.arnauto...@sematext.com> wrote: > Hi John, > You should be able to do that with custom update request processor chain and > https://lucene.apache.org/solr/6_6_0//solr-core/org/apache/solr/update/processor/AddSchemaFieldsUpdateProcessorFactory.html > > <https://lucene.apache.org/solr/6_6_0//solr-core/org/apache/solr/update/processor/AddSchemaFieldsUpdateProcessorFactory.html> > > HTH, > Emir > -- > Monitoring - Log Management - Alerting - Anomaly Detection > Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > > > >> On 19 Oct 2017, at 08:00, John Davis <johndavis925...@gmail.com> wrote: >> >> Hi, >> I know about the schemaless configuration defaulting to multivalued fields >> of the corresponding type. >> >> I was just wondering if there was a way to first detect if the incoming >> value is list or singleton, and based on it pick the corresponding types. >> Ideally if the value is an long then use tlong while if it is list of longs >> then use tlongS. >> >> Thanks! >> John >
