I wonder what does Solr stores in the document for fields which are not being used. And if the queries have a performance difference https://lucene.apache.org/solr/guide/6_6/defining-fields.html (A default value that will be added automatically to any document that does not have a value in this field when it is indexed. If this property is not specified, there is no default)
Deepak "The greatness of a nation can be judged by the way its animals are treated. Please stop cruelty to Animals, become a Vegan" +91 73500 12833 deic...@gmail.com Facebook: https://www.facebook.com/deicool LinkedIn: www.linkedin.com/in/deicool "Plant a Tree, Go Green" Make In India : http://www.makeinindia.com/home On Thu, May 10, 2018 at 9:10 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 5/10/2018 7:51 AM, Issei Nishigata wrote: > >> I am designing a schema. >> >> I calculated the number of the necessary field as trial, and found that I >> need at least more than 35000. >> I do not use all these fields in 1 document. >> I use 300 field each document at maximum, and do not use remaining 34700 >> fields. >> >> Does this way of using it affect performance such as retrieving and >> sorting? >> If it is affected, what kind of alternative idea do we have? >> > > There are no storage efficiency degradations from having fields defined > that aren't used in particular documents. > > It is likely that having so many fields is going to result in extremely > large and complex queries. That is the potential performance problem. > > The efficiency of each clause of the query will not be affected by having > several thousand fields unused in each document, but if your queries > include clauses for searching thousands of fields, then the query will run > slowly. If you are constructing relatively simple queries that only touch > a small number of fields, then that won't be a worry. > > Thanks, > Shawn > >
