honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-09 06:25:07 +00:00
Code Issues Packages Projects Releases Wiki Activity
10,037 Commits 7 Branches 6 Tags
Commit Graph

19 Commits

Author SHA1 Message Date
Clinton Gormley
cb00d4a542 Docs: Removed all the added/deprecated tags from 1.x 2014-09-26 21:04:42 +02:00
Ulrich Reffle
4ed52073fa Docs: A simple typo. 
Closes #7535
 2014-09-11 11:17:49 +02:00
Britta Weber
c5ff70bf43 function_score: add optional weight parameter per function 
Weights can be defined per function like this:

```
"function_score": {
    "functions": [
        {
            "filter": {},
            "FUNCTION": {},
            "weight": number
        }
        ...
```
If `weight` is given without `FUNCTION` then `weight` behaves like `boost_factor`.
This commit deprecates `boost_factor`.

The following is valid:

```
POST testidx/_search
{
  "query": {
    "function_score": {
      "weight": 2
    }
  }
}
POST testidx/_search
{
  "query": {
    "function_score": {
      "functions": [
        {
          "weight": 2
        },
        ...
      ]
    }
  }
}
POST testidx/_search
{
  "query": {
    "function_score": {
      "functions": [
        {
          "FUNCTION": {},
          "weight": 2
        },
        ...
      ]
    }
  }
}
POST testidx/_search
{
  "query": {
    "function_score": {
      "functions": [
        {
          "filter": {},
          "weight": 2
        },
        ...
      ]
    }
  }
}
POST testidx/_search
{
  "query": {
    "function_score": {
      "functions": [
        {
          "filter": {},
          "FUNCTION": {},
          "weight": 2
        },
        ...
      ]
    }
  }
}
```

The following is not valid:

```
POST testidx/_search
{
  "query": {
    "function_score": {
      "weight": 2,
      "FUNCTION(including boost_factor)": 2
    }
  }
}

POST testidx/_search
{
  "query": {
    "function_score": {
      "functions": [
        {
          "weight": 2,
          "boost_factor": 2
        }
      ]
    }
  }
}
````

closes #6955
closes #7137
 2014-09-01 11:04:40 +02:00
Ryan Ernst
65afa1d93b FunctionScore: Refactor RandomScoreFunction to be consistent, and return values in rang [0.0, 1.0] 
RandomScoreFunction previously relied on the order the documents were
iterated in from Lucene. This caused changes in ordering, with the same
seed, if documents moved to different segments. With this change, a
murmur32 hash of the _uid for each document is used as the "random"
value. Also, the hash is adjusted so as to only return values between
0.0 and 1.0 to enable easier manipulation to fit into users' scoring
models.

closes #6907, #7446
 2014-08-27 08:37:25 -07:00
Britta Weber
10201d511c [doc] Correct decay function equations in function_score description 
Impact of decay and scale was missing from the equations.

Closes #6983
 2014-07-23 17:33:22 +02:00
Konrad Feldmeier
48812ff1f2 Reflect that 'field_value_factor' is only in 1.2.x 
While the blogpost http://www.elasticsearch.org/blog/2014-04-02-this-week-in-elasticsearch/ states, that feature #5519 was
added to 1.x, the release notes for, e.g. v1.1.2, however tell otherwise.
Only the release notes for 1.2.0 list #5519 as a new feature.

Since the 1.x docs deprecate/discourage from using `_boost`, and seemingly give a migration example at
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/mapping-boost-field.html#function-score-instead-of-boost
users of 1.1.x should be warned.
 2014-07-23 15:49:03 +02:00
Clinton Gormley
a862732434 Docs: Typo 2014-07-21 18:51:49 +02:00
Steve Fuller
b800be891f [DOCS] fixed typo in fucntion-score query docs 2014-06-03 12:05:59 +02:00
Benjamin Devèze
6feeac98c8 s/boost_factor/boost in custom_filters_score doc 
I may be wrong but I think custom_filters_score used boost rather than boost factor?
 2014-05-06 16:15:36 +02:00
gabriel-tessier
48930c2950 [DOC] Fix typo in function score query documentation. 2014-05-02 23:44:56 +02:00
Simon Willnauer
f285ffc610 Multi value handling in decay functions 
Decay functions currently only use the first value in a field that contains
multiple values to compute the distance to the origin. Instead, it should
consider all distances if more values are in the field and then use
one of min/max/sum/avg which is defined by the user.

Relates to #3960
closes #5940
 2014-04-28 11:55:32 +02:00
Samuel Molinari
909cf4de44 Update function-score-query.asciidoc 2014-04-20 13:39:32 +02:00
Lee Hinman
8fbd1bdd48 Add the field_value_factor function to the function_score query 
The `field_value_factor` function uses the value of a field in the
document to influence the score.

A query that looks like:
{
  "query": {
    "function_score": {
      "query": {"match": { "body": "foo" }},
      "functions": [
        {
          "field_value_factor": {
            "field": "popularity",
            "factor": 1.1,
            "modifier": "square"
          }
        }
      ],
      "score_mode": "max",
      "boost_mode": "sum"
    }
  }
}

Would have the score modified by:

square(1.1 * doc['popularity'].value)

Closes #5519
 2014-03-27 14:29:37 -06:00
Clinton Gormley
93930d6dc7 Removed 0.90.* deprecation and addition notifications 
Closes #5052
 2014-02-07 20:52:49 +01:00
Britta Weber
34441f3897 fix naming in function_score 
- "boost" should be "boost_factor"
    - "mult" should be "multiply"

Also, store combine function names in ImmutableMap instead of iterating
over all possible names each time.

closes #3872 for master
 2013-10-14 14:56:59 +02:00
Britta Weber
b7c3b50909 add date field to decay function doc 2013-09-17 19:54:31 +02:00
Clinton Gormley
c2eb4a1c40 [DOCS] Tidied up function score 2013-09-16 15:57:08 +02:00
Clinton Gormley
2b3a762c27 [DOCS] Function score was added in 0.90.4 not 1.00.Beta 2013-09-05 11:25:06 +02:00
Clinton Gormley
765bd026f5 [DOCS] Added function score query 2013-09-04 23:20:55 +02:00