Boot-time Mapping Definitions #86
Comments
|
I am going to allow for mappings to be defined under the config/mappings location. Each mapping should be in its own file, and the file name should be [mappingName].json. For example, under config/mappings you will have Also, note that the mappings must exists on all nodes/servers in the cluster. |
|
Boot-time Mapping Definitions, closed by e5cd594. |
|
Change the default location to |
dadoonet
added a commit
that referenced
this issue
Jun 5, 2015
When a Snapshot does not exist, we should raise a `SnapshotMissingException`. Add also tests for GET/DELETE on non existing repo Closes #86. (cherry picked from commit 77ab672)
kblincoe
added a commit
to gwyneth-bassett/elasticsearch
that referenced
this issue
Mar 21, 2017
Unclaimed 23646
ClaudioMFreitas
pushed a commit
to ClaudioMFreitas/elasticsearch-1
that referenced
this issue
Nov 12, 2019
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
With this commit we raise the network timeout for all benchmarks (regardless whether they have specified client options before or not) from the previous default value of 60 seconds to 240 seconds. We have seen some bulk requests fail with a network timeout in recent benchmarks and hence we bump it so we don't skew results due to timeouts. Relates elastic#86
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Allow for mappings to be defined in a config file so that they will be pre-defined to the cluster when it starts up.
The text was updated successfully, but these errors were encountered: