Varun: Thanks! I don't so much care about making the field optional as having the docs in place, that's more important IMO. I'll leave whether it should be optional to people who, you know, understand the implications...
One request... In the documentation, a quick note on how to _use_ that field would be a Good Thing Thanks! On Tue, Aug 12, 2014 at 10:14 PM, Varun Thacker <[email protected]> wrote: > Hi Erick, > > Good that you brought it up. I started working on drafting out the > documentation for the Suggester. > > SOLR-5683 is the Jira for the documentation. This is what was written > originally - > "DocumentDictionaryFactory – user can specify suggestion field along with > optional weight and payload fields from their search index." > > Although like you said the weight field is currently not optional. > > Answering your question on what do they do - They are used for sorting the > results since there is no other relevance factor involved. > > For a user who doesn't have weight calculated for his entries, just simply > getting to use AnalyzingInfixSuggester or some other suggester by itself is > beneficial. If more people agree I could create a Jira and work on making > the weight field optional. > > > > > > > On Wed, Aug 13, 2014 at 9:43 AM, Erick Erickson <[email protected]> > wrote: > >> Upgrading from Solr 3.5 to 4.8 for a client and mucking around in >> solrconfig.xml. I thought Hey, let's uncomment the suggester just for yucks >> so they can try it out". >> >> Fine so far, but then I looked to try to figure out what part of their >> schema to use for the entry in the suggest component: >> <str name="weightField">price</str> >> >> and.... there isn't anything in any documentation that I can find. If I >> take it out I get an error at startup since it's a required field. For >> instance, it's not in the ref guide. Google doesn't help. Looking at the >> code also doesn't explain much, and isn't very friendly anyway. I _suspect_ >> that it's ok to have a bogus entry here since the code seems to return 0 if >> there's no field (on a very quick glance) in which case it seems like it's >> _not_ really required. >> >> So.. what happens if the field is absent? What kinds of values _should_ >> be in it? What do they do? and all that rot.... >> >> If we're going to require it, we should provide some guidance somewhere. >> Worth a JIRA? >> >> Erick >> > > > > -- > > > Regards, > Varun Thacker > http://www.vthacker.in/ >
