New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Warmers: Dedicated Norms/Terms warm options in mappings #4079

Closed
kimchy opened this Issue Nov 4, 2013 · 1 comment

Comments

Projects
None yet
3 participants
@kimchy
Member

kimchy commented Nov 4, 2013

Similar to the loading part in fielddata, where someone can configure if they are loaded eagerly or not, we should have the same option in mappings for norms, and for terms.

Idea regarding naming, within a field:

{
   "terms" : {"loading" : "lazy|eager"},
    "norms" : {"enabled" : false|true, "loading" : "lazy|eager"}
}

Note, the above will deprecate the omit_norms field mapping, and follows similar structure to the fileddata mapping config.

@s1monw

This comment has been minimized.

Show comment
Hide comment
@s1monw

s1monw Nov 13, 2013

Contributor

moved over to 0.90.8

Contributor

s1monw commented Nov 13, 2013

moved over to 0.90.8

@ghost ghost assigned jpountz Dec 20, 2013

jpountz added a commit to jpountz/elasticsearch that referenced this issue Dec 27, 2013

Eager norms loading options.
Norms can be eagerly loaded on a per-field basis by setting norms.loading to
`eager` instead of the default `lazy`:

```
"my_string_field" : {
  "type": "string",
  "norms": {
    "loading": "eager"
  }
}
```

In case this behavior should be applied to all fields, it is possible to change
the default value by setting `index.norms.loading` to `eager`.

Close #4079

@jpountz jpountz closed this in 9763d07 Jan 6, 2014

jpountz added a commit that referenced this issue Jan 6, 2014

Eager norms loading options.
Norms can be eagerly loaded on a per-field basis by setting norms.loading to
`eager` instead of the default `lazy`:

```
"my_string_field" : {
  "type": "string",
  "norms": {
    "loading": "eager"
  }
}
```

In case this behavior should be applied to all fields, it is possible to change
the default value by setting `index.norms.loading` to `eager`.

Close #4079

brusic added a commit to brusic/elasticsearch that referenced this issue Jan 19, 2014

Eager norms loading options.
Norms can be eagerly loaded on a per-field basis by setting norms.loading to
`eager` instead of the default `lazy`:

```
"my_string_field" : {
  "type": "string",
  "norms": {
    "loading": "eager"
  }
}
```

In case this behavior should be applied to all fields, it is possible to change
the default value by setting `index.norms.loading` to `eager`.

Close #4079

johtani added a commit to johtani/elasticsearch-solr-api that referenced this issue Jan 28, 2014

Change es version to 1.0.0.RC1
* Move RestRequest to be an abstract class elastic/elasticsearch#4683
* Change the version of es to 1.0.0.RC1
* Related DateFieldMapper elastic/elasticsearch#3806 , elastic/elasticsearch#4560 , elastic/elasticsearch#4079 , elastic/elasticsearch#4117 , elastic/elasticsearch#4521
* Redesigned the percolator engine elastic/elasticsearch#3173

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

Eager norms loading options.
Norms can be eagerly loaded on a per-field basis by setting norms.loading to
`eager` instead of the default `lazy`:

```
"my_string_field" : {
  "type": "string",
  "norms": {
    "loading": "eager"
  }
}
```

In case this behavior should be applied to all fields, it is possible to change
the default value by setting `index.norms.loading` to `eager`.

Close #4079
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment