: Would this mean that, for example, if we wanted to search productId (long) : we'd need to make a field type that had stopwords in it rather than simply : using (long)?
not really ... that's kind of a special usecase. if someone searches for a productId that's usually *all* they search for (1 "chunk" of input fro mthe query parser) so it's mandatory and produces a clause across all fields. It doesn't matter if the other fields have stopwords -- even if the productId happens to be a stop word, that just means it doesn't produce a clause on those "stop worded" fields, but it will will on your productId field. The only case where you might get into trouble is if someone searches for "the 123456" ... now you have two chunks of input, so the mm param comes into play you have no stopwords on your productId field so both "the" and "123456" produce clauses, but "the" isn't going to be found in your productId field, and because of stopwords it doens't exist in the other fields at all ... so you don't match anything. FWIW: if i remember right if you want to put numeric fields in the qf, i think you need *all* of them to be numeric and all of your input needs to be numeric, or you get exceptions from the FieldType (not the dismax parser) when people search for normal words. i always copyField productId into a productId_str field for purposes like this. -Hoss
