Setting username weight to 0.0 returns no results

[Jerod Santo]

Hey there-

Looks like my hntrends app is returning all 0s for hit counts these days. I have identified the culprit, but am not quite sure what changed to make it a problem. Somebody had advised me to set the weight for username to 0.0 if I wanted to exclude matches on usernames from the results. That used to work, but now it removes all hits. For instance:

http://api.thriftdb.com/api.hnsearch.com/items/_search?filter[queries][]=create_ts:[2011-10-01T00:00:00Z%20TO%202011-12-31T23:59:59Z]&q=coffeescript&limit=0&weights[username]=0.0

Returns 0 hits while:

http://api.thriftdb.com/api.hnsearch.com/items/_search?filter[queries][]=create_ts:[2011-10-01T00:00:00Z%20TO%202011-12-31T23:59:59Z]&q=coffeescript&limit=0

Returns 415 hits.

Am I doing it wrong or is this not even how to go about it?

Thanks.

[Andres Morey]

Hey Jerod,

Recently we changed the behavior of the weights. By default every field has a weight of 1.0. If you specify a weight on any field then the weights of the other fields are set to 0.0.

The logic behind that decision was that if someone is setting weights they they want more fine grained control over matching/relevancy.

Andres

[Jerod Santo]

Okay that makes sense.

Is there a way to accomplish my desired goal of excluding username matches from my results? Would I have to set its weight to 0 and then explicitly set the fields I want to match on back to 1?

-Jerod

(sent on the go)

[Andres Morey]

You can just set the other weights and 'username' will default to zero automatically.

Andres

[Jerod Santo]

That did the tricks. Thanks Andres!

[Andres Morey]

Awesome!