You could probably manage the schema by using dynamic fields. Also, enable lazy loading to avoid loading the values of the fields you do not care about.
Regards, Alex. Personal website: http://www.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Wed, Feb 5, 2014 at 12:10 PM, Mike L. <javaone...@yahoo.com> wrote: > > Hey Jack - > > Two types of queries: > > A) Return all docs that have a match for a particular value from a particular > field (fq=fieldname:value). Because of this I feel Im tied to defining all > the fields. No particular field matters more than another - depends on the > search context so hard to predict common searches. > > B) Return all docs whom have a particular value in one or more fields. > (small subset of the 3000). > > Ive been a bit spoiled with Solr being used to response times less than 50ms, > but in this case - search does not have to be fast. Also total index size > would be less than a 1GB and with less than 1M total docs. > > -Mike > > Sent from my iPhone > >> On Feb 4, 2014, at 10:38 PM, "Jack Krupansky" <j...@basetechnology.com> >> wrote: >> >> What will your queries be like? Will it be okay if they are relatively slow? >> I mean, how many of those 100 fields will you need to use in a typical (95th >> percentile) query? >> >> -- Jack Krupansky >> >> -----Original Message----- From: Mike L. >> Sent: Tuesday, February 4, 2014 10:00 PM >> To: solr-user@lucene.apache.org >> Subject: Max Limit to Schema Fields - Solr 4.X >> >> >> solr user group - >> >> I'm afraid I may have a scenario where I might need to define a few >> thousand fields in Solr. The context here is, this type of data is extremely >> granular and unfortunately cannot be grouped into logical groupings or >> aggregate fields because there is a need to know which granular field >> contains the data, and those field needs to be searchable. >> >> With that said, I expect each <doc> to not contain more than 100 fields with >> loaded data at a given time. Its just not clear of the few thousand fields >> created, which ones will have the data pertaining to that doc. >> >> I'm just wondering here if there is any defined limit to how many fields can >> be created within a schema? I'm sure the configuration maintenance of a >> schema like this would be a nightmare, but would like to know if its at all >> possible in the first place before It may be attempted. >> >> Thanks in advance - >> Mike
