content large_stringlengths 3 20.5k | url large_stringlengths 54 193 | branch large_stringclasses 4
values | source large_stringclasses 42
values | embeddings listlengths 384 384 | score float64 -0.21 0.65 |
|---|---|---|---|---|---|
[[norms]] === `norms` Norms store various normalization factors that are later used at query time in order to compute the score of a document relatively to a query. Although useful for scoring, norms also require quite a lot of disk (typically in the order of one byte per document per field in your index, even for docu... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/params/norms.asciidoc | 6.2 | elasticsearch-6-2 | [
0.003202128689736128,
0.04758279398083687,
-0.027600562199950218,
0.07633943855762482,
0.027051234617829323,
-0.0003300185489933938,
-0.029490379616618156,
0.010513249784708023,
0.07752375304698944,
-0.012181821279227734,
-0.05472097173333168,
0.06838682293891907,
0.07280443608760834,
0.01... | 0.013586 |
[[mapping-index-field]] === `\_index` field When performing queries across multiple indexes, it is sometimes desirable to add query clauses that are associated with documents of only certain indexes. The `\_index` field allows matching on the index a document was indexed into. Its value is accessible in `term`, or `ter... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/index-field.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.024036547169089317,
0.03410160169005394,
0.06674393266439438,
0.07063544541597366,
0.00367524242028594,
0.05831187218427658,
0.020267147570848465,
-0.0016559214564040303,
0.060235895216464996,
-0.019952330738306046,
-0.03388134017586708,
0.011958394199609756,
0.02569688856601715,
-0.011... | 0.097113 |
[[mapping-meta-field]] === `\_meta` field A mapping type can have custom meta data associated with it. These are not used at all by Elasticsearch, but can be used to store application-specific metadata, such as the class that a document belongs to: [source,js] -------------------------------------------------- PUT my\_... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/meta-field.asciidoc | 6.2 | elasticsearch-6-2 | [
0.09315945208072662,
0.10726386308670044,
0.024067504331469536,
0.00392128387466073,
0.014825191348791122,
0.025952577590942383,
0.006450650282204151,
0.08729495108127594,
0.01286584697663784,
-0.007617143914103508,
-0.057202957570552826,
-0.024734994396567345,
-0.030372103676199913,
0.008... | 0.058777 |
[[mapping-type-field]] === `\_type` field deprecated[6.0.0,See <>] Each document indexed is associated with a <> (see <>) and an <>. The `\_type` field is indexed in order to make searching by type name fast. The value of the `\_type` field is accessible in queries, aggregations, scripts, and when sorting: [source,js] ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/type-field.asciidoc | 6.2 | elasticsearch-6-2 | [
0.005498094949871302,
0.03496861085295677,
0.10820195078849792,
0.10645423084497452,
-0.00038492705789394677,
0.03292747586965561,
-0.007333142217248678,
0.020441101863980293,
0.07812446355819702,
-0.009031648747622967,
-0.03781747817993164,
0.06554492563009262,
-0.0498817078769207,
-0.020... | 0.062818 |
[[mapping-uid-field]] === `\_uid` field ifdef::asciidoctor[] deprecated::[6.0.0, "Now that types have been removed, documents are uniquely identified by their `\_id` and the `\_uid` field has only been kept as a view over the `\_id` field for backward compatibility."] endif::[] ifndef::asciidoctor[] deprecated[6.0.0, N... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/uid-field.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.06985855102539062,
0.050375137478113174,
-0.009531657211482525,
0.07029584795236588,
0.014054222032427788,
0.013292891904711723,
0.01644032821059227,
-0.018303746357560158,
0.04999150335788727,
-0.045403990894556046,
0.05515391379594803,
0.027423646301031113,
-0.03353816270828247,
-0.03... | 0.168473 |
[[mapping-field-names-field]] === `\_field\_names` field The `\_field\_names` field indexes the names of every field in a document that contains any value other than `null`. This field is used by the <> query to find documents that either have or don't have any non-+null+ value for a particular field. The value of the ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/field-names-field.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.019780999049544334,
0.09109273552894592,
0.0463053360581398,
0.0816771537065506,
0.005564066115766764,
-0.0015734517946839333,
0.006139250472187996,
-0.008405589498579502,
0.07629217207431793,
-0.025853009894490242,
-0.009775958955287933,
-0.043911319226026535,
0.014782288111746311,
-0.... | 0.058919 |
[[mapping-source-field]] === `\_source` field The `\_source` field contains the original JSON document body that was passed at index time. The `\_source` field itself is not indexed (and thus is not searchable), but it is stored so that it can be returned when executing \_fetch\_ requests, like <> or <>. [[disable-sour... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/source-field.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.07622167468070984,
0.10643109679222107,
0.03276168182492256,
0.08645542711019516,
0.05182184651494026,
-0.005886666476726532,
-0.031641025096178055,
-0.03590007498860359,
0.10740505158901215,
-0.043638087809085846,
0.015243595466017723,
0.09076378494501114,
0.008103789761662483,
-0.0516... | 0.055808 |
[[mapping-all-field]] === `\_all` field ifdef::asciidoctor[] deprecated::[6.0.0, "`\_all` may no longer be enabled for indices created in 6.0+, use a custom field and the mapping `copy\_to` parameter"] endif::[] ifndef::asciidoctor[] deprecated[6.0.0, `\_all` may no longer be enabled for indices created in 6.0+, use a ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/all-field.asciidoc | 6.2 | elasticsearch-6-2 | [
0.0437953919172287,
0.04493483528494835,
-0.06271534413099289,
0.02180747129023075,
0.026388883590698242,
0.02901899814605713,
-0.01223259512335062,
-0.0034929884131997824,
-0.02937428280711174,
-0.04723237454891205,
0.09866262972354889,
-0.050950583070516586,
-0.05593520775437355,
-0.0785... | 0.149158 |
field in `type\_1` is disabled. <2> The `\_all` field in `type\_2` is enabled. If the `\_all` field is enabled, then URI search requests and the `query\_string` and `simple\_query\_string` queries can automatically use it for queries (see <>). You can configure them to use a different field with the `index.query.defaul... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/all-field.asciidoc | 6.2 | elasticsearch-6-2 | [
0.010914809070527554,
0.025462055578827858,
0.0544971264898777,
0.08514624834060669,
-0.04978325590491295,
0.0367819145321846,
-0.002761734649538994,
0.027093004435300827,
0.03792731463909149,
-0.04623464122414589,
-0.03743521496653557,
0.009059960953891277,
-0.002791099715977907,
-0.02187... | 0.020312 |
true} } } } PUT myindex/mytype/1 { "first\_name": "John", "last\_name": "Smith" } GET \_search { "query": { "match": { "\_all": "John Smith" <1> } }, "highlight": { "fields": { "\*\_name": { <2> "require\_field\_match": false <3> } } } } -------------------------------- // TEST[skip:\_all is no longer allowed] // CONSO... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/all-field.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.05558152496814728,
0.05366065725684166,
0.06498553603887558,
0.08565263450145721,
0.045737460255622864,
0.02234196476638317,
0.08904176205396652,
-0.036529988050460815,
-0.008284023962914944,
-0.021374471485614777,
-0.04592413827776909,
-0.03245049715042114,
0.05641153082251549,
-0.0543... | 0.072406 |
[[mapping-id-field]] === `\_id` field Each document has an `\_id` that uniquely identifies it, which is indexed so that documents can be looked up either with the <> or the <>. NOTE: This was not the case with pre-6.0 indices due to the fact that they supported multiple types, so the `\_type` and `\_id` were merged int... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/id-field.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.051392339169979095,
0.07696669548749924,
0.05319980904459953,
0.1119270920753479,
-0.004939567763358355,
0.06181347370147705,
-0.00649402616545558,
0.017901895567774773,
0.07153447717428207,
-0.03344842046499252,
-0.043948180973529816,
0.053879063576459885,
0.0029414885211735964,
-0.022... | 0.080956 |
[[mapping-routing-field]] === `\_routing` field A document is routed to a particular shard in an index using the following formula: shard\_num = hash(\_routing) % num\_primary\_shards The default value used for `\_routing` is the document's <>. Custom routing patterns can be implemented by specifying a custom `routing`... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/routing-field.asciidoc | 6.2 | elasticsearch-6-2 | [
0.00004566106872516684,
0.05162130668759346,
0.013920646160840988,
0.04304014891386032,
-0.04457331448793411,
-0.02555849961936474,
-0.008340518921613693,
0.0036064297892153263,
0.07880713045597076,
-0.021177180111408234,
-0.028513526543974876,
0.03484161198139191,
0.00015208830882329494,
... | 0.037582 |
partitioned index will have the following limitations: \* Mappings with <> relationships cannot be created within it. \* All mappings within the index must have the `\_routing` field marked as required. | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/mapping/fields/routing-field.asciidoc | 6.2 | elasticsearch-6-2 | [
0.02912772446870804,
-0.04572395980358124,
0.039767343550920486,
0.05329219251871109,
-0.03744782879948616,
-0.005922114010900259,
-0.06896327435970306,
-0.02983086183667183,
-0.042848192155361176,
-0.029455384239554405,
-0.027253640815615654,
-0.01917627826333046,
0.006195331923663616,
0.... | 0.035127 |
[[cluster-nodes-usage]] == Nodes Feature Usage [float] === Nodes usage The cluster nodes usage API allows to retrieve information on the usage of features for each node. [source,js] -------------------------------------------------- GET \_nodes/usage GET \_nodes/nodeId1,nodeId2/usage -----------------------------------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/nodes-usage.asciidoc | 6.2 | elasticsearch-6-2 | [
0.027179012075066566,
0.06910721957683563,
-0.04453902691602707,
0.0993085503578186,
0.08638086169958115,
-0.05489443987607956,
0.07243449240922928,
-0.029457639902830124,
-0.006595938932150602,
-0.013039296492934227,
0.025656690821051598,
-0.073907271027565,
0.006948536727577448,
-0.05632... | 0.126252 |
[[cluster-state]] == Cluster State The cluster state API allows to get a comprehensive state information of the whole cluster. [source,js] -------------------------------------------------- GET /\_cluster/state -------------------------------------------------- // CONSOLE The response provides the cluster name, the tot... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/state.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.0367809496819973,
0.03751043230295181,
-0.019317902624607086,
0.10045143961906433,
0.06774059683084488,
-0.02399136871099472,
-0.006704482715576887,
-0.018176881596446037,
-0.00562515202909708,
-0.028982384130358696,
-0.05322369560599327,
-0.06135992333292961,
0.0029632551595568657,
-0.... | 0.140422 |
[[cluster-nodes-info]] == Nodes Info The cluster nodes info API allows to retrieve one or more (or all) of the cluster nodes information. [source,js] -------------------------------------------------- GET /\_nodes GET /\_nodes/nodeId1,nodeId2 -------------------------------------------------- // CONSOLE The first comma... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/nodes-info.asciidoc | 6.2 | elasticsearch-6-2 | [
0.012770963832736015,
0.029027175158262253,
-0.0339961051940918,
0.0942210927605629,
0.09708043932914734,
-0.04209768772125244,
0.016939397901296616,
-0.01679830625653267,
0.00793296005576849,
-0.018912402912974358,
0.028687752783298492,
-0.059944964945316315,
0.011806377209722996,
-0.1061... | 0.141304 |
"lang-painless", "version": "{version}", "description": "An easy, safe and fast scripting language for Elasticsearch", "classname": "org.elasticsearch.painless.PainlessPlugin", "has\_native\_controller": false } ] } } } -------------------------------------------------- // TESTRESPONSE[s/"\_nodes": \.\.\./"\_nodes": $b... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/nodes-info.asciidoc | 6.2 | elasticsearch-6-2 | [
0.026086999103426933,
0.02052375115454197,
-0.02396528795361519,
0.05712507665157318,
0.001082560163922608,
-0.008294148370623589,
0.00227834889665246,
-0.007496867794543505,
0.027454042807221413,
0.02876066230237484,
0.03605460003018379,
-0.05267985910177231,
0.01017296127974987,
0.019384... | 0.113425 |
[[cluster-nodes-stats]] == Nodes Stats [float] === Nodes statistics The cluster nodes stats API allows to retrieve one or more (or all) of the cluster nodes statistics. [source,js] -------------------------------------------------- GET /\_nodes/stats GET /\_nodes/nodeId1,nodeId2/stats ----------------------------------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/nodes-stats.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.019298484548926353,
0.00585069740191102,
-0.07984911650419235,
0.1045588031411171,
0.04859616979956627,
-0.029526589438319206,
-0.0012628019321709871,
-0.00022818623983766884,
-0.004555216524749994,
0.0015525890048593283,
0.013559511862695217,
-0.0843954086303711,
0.03159444406628609,
-... | 0.115755 |
since starting Elasticsearch. `fs.io\_stats.read\_operations` (Linux only):: The total number of read operations for across all devices used by Elasticsearch completed since starting Elasticsearch. `fs.io\_stats.write\_operations` (Linux only):: The total number of write operations across all devices used by Elasticsea... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/nodes-stats.asciidoc | 6.2 | elasticsearch-6-2 | [
0.06978330761194229,
0.004743639845401049,
-0.03136759623885155,
0.08534161746501923,
0.051912739872932434,
-0.08595979958772659,
0.00915642362087965,
0.06856238096952438,
0.06274398416280746,
0.08290877938270569,
-0.05081780254840851,
-0.01902616396546364,
-0.016822196543216705,
-0.033333... | 0.182454 |
and stats must be readable from `/sys/fs/cgroup/cpu` and `/sys/fs/cgroup/cpuacct`. [float] [[process-stats]] ==== Process statistics The `process` flag can be set to retrieve statistics that concern the current running process: `process.timestamp`:: Last time the process statistics have been refreshed `process.open\_fi... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/nodes-stats.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.03516274690628052,
-0.006596764549612999,
-0.12703806161880493,
0.014310473576188087,
0.027055298909544945,
-0.08021464198827744,
0.016699664294719696,
0.11088836193084717,
-0.0350167416036129,
0.021730635315179825,
-0.007241382263600826,
-0.08233028650283813,
-0.0009479033178649843,
-0... | 0.153435 |
[[cluster-reroute]] == Cluster Reroute The reroute command allows for manual changes to the allocation of individual shards in the cluster. For example, a shard can be moved from one node to another explicitly, an allocation can be cancelled, and an unassigned shard can be explicitly allocated to a specific node. Here ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/reroute.asciidoc | 6.2 | elasticsearch-6-2 | [
0.03957674279808998,
-0.04961497336626053,
0.004164620768278837,
0.061602361500263214,
-0.0016208336455747485,
-0.0013648037565872073,
-0.05103188008069992,
-0.0715537816286087,
0.055232640355825424,
0.026230894029140472,
-0.02517327107489109,
-0.0017730406252667308,
0.025275563821196556,
... | 0.049484 |
query parameter, which will attempt a single retry round for these shards. [float] === Forced allocation on unrecoverable errors Two more commands are available that allow the allocation of a primary shard to a node. These commands should however be used with extreme care, as primary shard allocation is usually fully a... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/reroute.asciidoc | 6.2 | elasticsearch-6-2 | [
0.04204144701361656,
0.009729748591780663,
0.060520488768815994,
0.0810735672712326,
0.009404472075402737,
-0.008725900202989578,
-0.03714607656002045,
-0.05445977672934532,
0.08258914202451706,
0.061232905834913254,
-0.008044098503887653,
0.014795612543821335,
0.07043633610010147,
-0.0390... | 0.060761 |
[[tasks]] == Task Management API beta[The Task Management API is new and should still be considered a beta feature. The API may change in ways that are not backwards compatible] [float] === Current Tasks Information The task management API allows to retrieve information about the tasks currently executing on one or mor... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/tasks.asciidoc | 6.2 | elasticsearch-6-2 | [
0.0031110274139791727,
-0.041142478585243225,
-0.03999795764684677,
0.10868024826049805,
0.07667529582977295,
-0.02662004344165325,
0.003729658666998148,
-0.02729634754359722,
-0.006663532927632332,
0.041941020637750626,
-0.050139281898736954,
-0.03372075408697128,
-0.010016006417572498,
-... | 0.143541 |
// CONSOLE Tasks can be also listed using \_cat version of the list tasks command, which accepts the same arguments as the standard list tasks command. [source,js] -------------------------------------------------- GET \_cat/tasks GET \_cat/tasks?detailed -------------------------------------------------- // CONSOLE [f... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/tasks.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.05321326479315758,
0.04104771465063095,
-0.03690878301858902,
0.0771641656756401,
0.027346253395080566,
-0.008739921264350414,
0.03198416158556938,
-0.0041269767098128796,
0.07955485582351685,
0.025083616375923157,
-0.02014847844839096,
0.02893119305372238,
-0.03837631270289421,
-0.0228... | 0.086571 |
[[cluster-pending]] == Pending cluster tasks The pending cluster tasks API returns a list of any cluster-level changes (e.g. create index, update mapping, allocate or fail shard) which have not yet been executed. NOTE: This API returns a list of any pending updates to the cluster state. These are distinct from the task... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/pending.asciidoc | 6.2 | elasticsearch-6-2 | [
0.0005159779684618115,
-0.03009631857275963,
-0.0057253530248999596,
0.1077752634882927,
0.06439212709665298,
-0.05746839568018913,
0.01997925341129303,
-0.08991004526615143,
0.08864455670118332,
0.04778984934091568,
-0.007044478785246611,
-0.009876745752990246,
-0.02220463566482067,
-0.03... | 0.172438 |
[[cluster-remote-info]] == Remote Cluster Info The cluster remote info API allows to retrieve all of the configured remote cluster information. [source,js] ---------------------------------- GET /\_remote/info ---------------------------------- // CONSOLE This command returns returns connection and endpoint information... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/remote-info.asciidoc | 6.2 | elasticsearch-6-2 | [
0.015182366594672203,
0.0011185372713953257,
-0.06708855926990509,
0.04589328542351723,
0.036973342299461365,
-0.01455075852572918,
-0.043577373027801514,
-0.0038321586325764656,
0.05508503317832947,
0.04228832200169563,
0.007606271654367447,
-0.008724575862288475,
0.004428190179169178,
-0... | 0.109399 |
[[cluster-allocation-explain]] == Cluster Allocation Explain API The purpose of the cluster allocation explain API is to provide explanations for shard allocations in the cluster. For unassigned shards, the explain API provides an explanation for why the shard is unassigned. For assigned shards, the explain API provide... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/allocation-explain.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.0020242901518940926,
0.000887187197804451,
-0.011236507445573807,
0.08781391382217407,
0.058154504746198654,
-0.04129587486386299,
-0.029254386201500893,
-0.034080442041158676,
0.07456592470407486,
-0.027614200487732887,
-0.027901766821742058,
-0.03417663276195526,
0.02807462215423584,
... | 0.132241 |
about disk usage and shard sizes by setting the `include\_disk\_info` parameter to `true`: [source,js] -------------------------------------------------- GET /\_cluster/allocation/explain?include\_disk\_info=true -------------------------------------------------- // CONSOLE Additionally, if you would like to include al... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/allocation-explain.asciidoc | 6.2 | elasticsearch-6-2 | [
0.03555867075920105,
0.01920933835208416,
0.0010331672383472323,
0.050729695707559586,
0.052745893597602844,
-0.07268624752759933,
-0.014311464503407478,
0.024285171180963516,
0.05550971254706383,
0.0374678298830986,
0.0031589665450155735,
-0.01130012609064579,
0.0061750756576657295,
-0.06... | 0.034479 |
index setting [index.routing.allocation.include] filters [\_name:\"non\_existent\_node\"]" } ] } ] } -------------------------------------------------- // NOTCONSOLE <1> Whether the shard is allowed to remain on its current node <2> The deciders that factored into the decision of why the shard is not allowed to remain ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/allocation-explain.asciidoc | 6.2 | elasticsearch-6-2 | [
0.010606774128973484,
-0.004589436110109091,
0.009082939475774765,
0.06898189336061478,
0.06046724691987038,
-0.02877049706876278,
0.0034105589147657156,
-0.09165692329406738,
0.07166153937578201,
-0.027099059894680977,
-0.024855662137269974,
0.0007580507081001997,
0.03977049142122269,
-0.... | 0.088233 |
[[cluster-health]] == Cluster Health The cluster health API allows to get a very simple status on the health of the cluster. For example, on a quiet single node cluster with a single index with 5 shards and one replica, this: [source,js] -------------------------------------------------- GET \_cluster/health ----------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/health.asciidoc | 6.2 | elasticsearch-6-2 | [
0.007813587784767151,
0.03898267447948456,
-0.025983499363064766,
0.07651248574256897,
0.054203588515520096,
-0.05002922564744949,
-0.041169747710227966,
-0.02185845375061035,
0.052357129752635956,
-0.044679783284664154,
-0.017157496884465218,
-0.03665760159492493,
0.001012966618873179,
-0... | 0.173802 |
[[cluster-stats]] == Cluster Stats The Cluster Stats API allows to retrieve statistics from a cluster wide perspective. The API returns basic index metrics (shard numbers, store size, memory usage) and information about the current nodes that form the cluster (number, roles, os, jvm versions, memory usage, cpu and inst... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/stats.asciidoc | 6.2 | elasticsearch-6-2 | [
0.028464199975132942,
0.024988751858472824,
-0.09193744510412216,
0.10487256944179535,
0.04761660844087601,
-0.020511718466877937,
-0.009598756209015846,
0.0074269697070121765,
0.04282382130622864,
-0.019019974395632744,
0.03547605872154236,
-0.061936620622873306,
0.03407255932688713,
-0.0... | 0.115657 |
[[cluster-update-settings]] == Cluster Update Settings Allows to update cluster wide specific settings. Settings updated can either be persistent (applied across restarts) or transient (will not survive a full cluster restart). Here is an example: [source,js] -------------------------------------------------- PUT /\_cl... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/update-settings.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.024486472830176353,
-0.021992981433868408,
-0.06778918951749802,
0.07555786520242691,
0.0008843620307743549,
-0.011612758971750736,
-0.04176550358533859,
0.0031030119862407446,
0.0036239020992070436,
-0.013533983379602432,
0.020690560340881348,
0.0035660970024764538,
-0.024296769872307777... | 0.15947 |
[[cluster-nodes-hot-threads]] == Nodes hot\_threads An API allowing to get the current hot threads on each node in the cluster. Endpoints are `/\_nodes/hot\_threads`, and `/\_nodes/{nodesIds}/hot\_threads`. The output is plain text with a breakdown of each node's top hot threads. Parameters allowed are: [horizontal] `t... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/cluster/nodes-hot-threads.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.03113335184752941,
-0.038508858531713486,
-0.07360353320837021,
0.09463255852460861,
0.05463007465004921,
-0.02385212481021881,
0.0021493851672858,
-0.08145098388195038,
-0.005405915901064873,
0.007646644487977028,
0.021680153906345367,
-0.058442071080207825,
-0.0017692859983071685,
-0.... | 0.250556 |
[[rolling-upgrades]] == Rolling upgrades A rolling upgrade allows an Elasticsearch cluster to be upgraded one node at a time so upgrading does not interrupt service. Running multiple versions of Elasticsearch in the same cluster beyond the duration of an upgrade is not supported, as shards cannot be replicated from upg... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/upgrade/rolling_upgrade.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.001712427823804319,
-0.0001193605930893682,
0.04492470622062683,
-0.01322268694639206,
0.09107603877782822,
-0.07092683762311935,
-0.08453766256570816,
-0.07823659479618073,
0.002232524799183011,
0.058841366320848465,
-0.004228790290653706,
0.05760566517710686,
0.037754714488983154,
-0.... | 0.05256 |
can monitor the recovery status of individual shards by submitting a <> request: [source,sh] -------------------------------------------------- GET \_cat/recovery -------------------------------------------------- // CONSOLE If you stopped indexing, it is safe to resume indexing as soon as recovery completes. -- . \*Re... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/upgrade/rolling_upgrade.asciidoc | 6.2 | elasticsearch-6-2 | [
0.010841762647032738,
-0.04161906987428665,
0.05542482063174248,
0.06967669725418091,
0.06298930197954178,
-0.05014363303780556,
-0.06701914221048355,
-0.04921964183449745,
-0.026374202221632004,
0.00197589211165905,
-0.0010384886991232634,
0.07902712374925613,
-0.008148676715791225,
-0.04... | 0.031518 |
[TIP] ================================================ When you extract the zip or tarball packages, the `elasticsearch-n.n.n` directory contains the Elasticsearh `config`, `data`, `logs` and `plugins` directories. We recommend moving these directories out of the Elasticsearch directory so that there is no chance of de... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/upgrade/set-paths-tip.asciidoc | 6.2 | elasticsearch-6-2 | [
0.06258269399404526,
-0.002534186001867056,
0.04255485534667969,
-0.0476238839328289,
0.04183356091380119,
-0.0372837595641613,
-0.05193262919783592,
-0.023019196465611458,
0.0068437159061431885,
0.07100774347782135,
-0.014595615677535534,
0.008491232059895992,
-0.017757315188646317,
0.008... | 0.014748 |
When you shut down a node, the allocation process waits for `index.unassigned.node\_left.delayed\_timeout` (by default, one minute) before starting to replicate the shards on that node to other nodes in the cluster, which can involve a lot of I/O. Since the node is shortly going to be restarted, this I/O is unnecessary... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/upgrade/disable-shard-alloc.asciidoc | 6.2 | elasticsearch-6-2 | [
0.036444131284952164,
0.042535848915576935,
0.03185329958796501,
0.13202542066574097,
0.09041902422904968,
-0.06583984941244125,
-0.0755624771118164,
-0.08142922073602676,
0.07824679464101791,
0.01666269637644291,
-0.05493605136871338,
0.07599952071905136,
-0.049339745193719864,
-0.0533657... | 0.074329 |
\* If you are running Elasticsearch with `systemd`: + [source,sh] -------------------------------------------------- sudo systemctl stop elasticsearch.service -------------------------------------------------- \* If you are running Elasticsearch with SysV `init`: + [source,sh] ------------------------------------------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/upgrade/shut-down-node.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.009882177226245403,
0.058415792882442474,
-0.013206305913627148,
-0.055894456803798676,
0.030651912093162537,
-0.06390035897493362,
-0.03819699212908745,
-0.0029404768720269203,
0.06041866913437843,
0.04559057578444481,
-0.020831139758229256,
-0.02599848434329033,
-0.006450183689594269,
... | 0.10109 |
[[reindex-upgrade]] == Reindex before upgrading Elasticsearch can read indices created in the \*previous major version\*. Older indices must be reindexed or deleted. Elasticsearch 6.x can use indices created in Elasticsearch 5.x, but not those created in Elasticsearch 2.x or before. Elasticsearch 5.x can use indices cr... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/upgrade/reindex_upgrade.asciidoc | 6.2 | elasticsearch-6-2 | [
0.06018749997019768,
-0.06781839579343796,
0.09774383157491684,
0.020991889759898186,
0.06038994714617729,
-0.044657886028289795,
-0.08197740465402603,
-0.08631673455238342,
-0.027006374672055244,
0.06043605878949165,
-0.012283219955861568,
-0.029786787927150726,
-0.029631441459059715,
-0.... | 0.048346 |
to a new 6.x cluster. This enables you move to 6.x from a pre-5.6 cluster without interrupting service. [WARNING] ============================================= Elasticsearch provides backwards compatibility support that enables indices from the previous major version to be upgraded to the current major version. Skippin... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/upgrade/reindex_upgrade.asciidoc | 6.2 | elasticsearch-6-2 | [
0.047614794224500656,
-0.08150080591440201,
0.06396418809890747,
0.017477843910455704,
0.0658663734793663,
0.006180187687277794,
-0.1053190752863884,
-0.08230392634868622,
-0.0485217459499836,
0.03135604411363602,
-0.03565342351794243,
0.03724692761898041,
-0.06312230229377747,
-0.05977644... | 0.051743 |
To upgrade using a <> or <> package: \* Use `rpm` or `dpkg` to install the new package. All files are installed in the appropriate location for the operating system and Elasticsearch config files are not overwritten. To upgrade using a zip or compressed tarball: .. Extract the zip or tarball to a \_new\_ directory. Thi... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/upgrade/upgrade-node.asciidoc | 6.2 | elasticsearch-6-2 | [
0.07032197713851929,
-0.029241355136036873,
0.04151976481080055,
-0.05517012998461723,
0.06255774945020676,
-0.02654658444225788,
-0.09272337704896927,
0.04596409574151039,
0.003933717962354422,
0.07133865356445312,
-0.006832456216216087,
0.022678952664136887,
-0.005913295317441225,
-0.027... | -0.025394 |
[[restart-upgrade]] == Full cluster restart upgrade A full cluster restart upgrade requires that you shut all nodes in the cluster down, upgrade them, and restart the cluster. A full cluster restart was required when upgrading to major versions prior to 6.x. Elasticsearch 6.x supports <> from \*Elasticsearch 5.6\*. Upg... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/upgrade/cluster_restart.asciidoc | 6.2 | elasticsearch-6-2 | [
0.07330156862735748,
-0.027100397273898125,
0.021931087598204613,
0.01120415236800909,
0.03214024007320404,
0.014513399451971054,
-0.14398041367530823,
-0.07070966809988022,
0.0008388165733776987,
0.05242270231246948,
-0.01302406471222639,
0.0047477539628744125,
-0.017963320016860962,
-0.0... | 0.076846 |
[[indices-refresh]] == Refresh The refresh API allows to explicitly refresh one or more index, making all operations performed since the last refresh available for search. The (near) real-time capabilities depend on the index engine used. For example, the internal one requires refresh to be called, but by default a ref... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/refresh.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.07659706473350525,
-0.011151747778058052,
-0.03487908095121384,
0.12981393933296204,
0.028087476268410683,
-0.04426067695021629,
0.02373451367020607,
-0.055978525429964066,
0.10700225830078125,
-0.01635020785033703,
0.009377317503094673,
0.011778523214161396,
-0.015799151733517647,
-0.0... | 0.067881 |
[[indices-get-field-mapping]] == Get Field Mapping The get field mapping API allows you to retrieve mapping definitions for one or more fields. This is useful when you do not need the complete type mapping returned by the <> API. For example, consider the following mapping: [source,js] ---------------------------------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/get-field-mapping.asciidoc | 6.2 | elasticsearch-6-2 | [
0.03201686218380928,
0.09870215505361557,
0.053956057876348495,
0.07119680941104889,
-0.025321219116449356,
0.007624858524650335,
-0.012871953658759594,
0.03311869502067566,
0.06348487734794617,
-0.05064814165234566,
-0.05493110045790672,
-0.033225495368242264,
-0.02628524787724018,
0.0169... | 0.022655 |
[[indices-aliases]] == Index Aliases APIs in Elasticsearch accept an index name when working against a specific index, and several indices when applicable. The index aliases API allows aliasing an index with a name, with all APIs automatically converting the alias name to the actual index name. An alias can also be map... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/aliases.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.06068165600299835,
0.03831857442855835,
0.0431768074631691,
0.05669030919671059,
0.00820064265280962,
-0.009255290031433105,
0.018641943112015724,
0.020584946498274803,
0.10685604065656662,
-0.008957711048424244,
-0.05455038696527481,
-0.04959659278392792,
0.003936161752790213,
0.021737... | 0.109841 |
the same index. The filter can be defined using Query DSL and is applied to all Search, Count, Delete By Query and More Like This operations with this alias. To create a filtered alias, first we need to ensure that the fields already exist in the mapping: [source,js] -------------------------------------------------- P... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/aliases.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.051650695502758026,
0.041225846856832504,
0.026199011132121086,
0.060941677540540695,
-0.04357821121811867,
-0.004140828270465136,
0.08215594291687012,
0.03664717823266983,
0.04374871030449867,
-0.061302050948143005,
-0.03926444053649902,
-0.0459587499499321,
0.0021566322539001703,
-0.0... | 0.019714 |
"current\_day" : {}, "2016" : { "filter" : { "term" : {"year" : 2016 } } } } } -------------------------------------------------- // CONSOLE [float] [[deleting]] === Delete aliases The rest endpoint is: `/{index}/\_alias/{name}` where [horizontal] `index`:: `\* | \_all | glob pattern | name1, name2, …` `name`:: `\* | \... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/aliases.asciidoc | 6.2 | elasticsearch-6-2 | [
0.0048217689618468285,
0.09555965662002563,
0.050662435591220856,
0.006109972018748522,
0.02465660683810711,
0.0047812736593186855,
0.010929462499916553,
-0.01888228952884674,
0.04369423910975456,
0.014766767621040344,
-0.013599193654954433,
-0.06686776876449585,
0.005284758750349283,
-0.0... | 0.057119 |
[[indices-analyze]] == Analyze Performs the analysis process on a text and return the tokens breakdown of the text. Can be used without specifying an index against one of the many built in analyzers: [source,js] -------------------------------------------------- GET \_analyze { "analyzer" : "standard", "text" : "this i... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/analyze.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.040462009608745575,
0.10841081291437149,
-0.06449015438556671,
0.04319038614630699,
0.01247387658804655,
-0.0011528943432494998,
0.07100025564432144,
-0.002863748464733362,
0.09981260448694229,
-0.03660382702946663,
-0.08438502997159958,
-0.026485305279493332,
-0.016899587586522102,
-0.... | 0.116253 |
"output", "start\_offset" : 9, "end\_offset" : 15, "type" : "", "position" : 1 } ] }, "tokenfilters" : [ { "name" : "snowball", "tokens" : [ { "token" : "detail", "start\_offset" : 0, "end\_offset" : 8, "type" : "", "position" : 0, "keyword" : false <1> }, { "token" : "output", "start\_offset" : 9, "end\_offset" : 15, ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/analyze.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.02211950719356537,
0.07906574010848999,
0.01996496692299843,
0.01864859275519848,
0.003227662295103073,
0.03318457305431366,
0.0537789985537529,
0.03614484518766403,
0.013602633960545063,
-0.020346423611044884,
-0.007971730083227158,
-0.07974397391080856,
0.03949640691280365,
-0.0286758... | 0.041133 |
[[indices-rollover-index]] == Rollover Index The rollover index API rolls an alias over to a new index when the existing index is considered to be too large or too old. The API accepts a single alias name and a list of `conditions`. The alias must point to a single index only. If the index satisfies the specified condi... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/rollover-index.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.053340356796979904,
0.08508794009685516,
0.07260443270206451,
0.06533293426036835,
0.007882575504481792,
-0.015200034715235233,
-0.006295115686953068,
0.04694551229476929,
0.04713528975844383,
0.06377742439508438,
-0.023462291806936264,
0.03202512487769127,
-0.014322442933917046,
0.0133... | 0.082661 |
// CONSOLE // TEST[continued] // TEST[s/now/2016.10.31||/] [float] === Defining the new index The settings, mappings, and aliases for the new index are taken from any matching <>. Additionally, you can specify `settings`, `mappings`, and `aliases` in the body of the request, just like the <> API. Values specified in th... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/rollover-index.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.021288041025400162,
0.08660656213760376,
0.0643734261393547,
0.037841375917196274,
-0.012862381525337696,
-0.0357014425098896,
-0.0406414233148098,
0.011080772615969181,
0.03645651414990425,
0.023705193772912025,
-0.015025625005364418,
0.013770229183137417,
-0.0011765192029997706,
0.035... | 0.021959 |
[[indices-put-mapping]] == Put Mapping The PUT mapping API allows you to add fields to an existing index or to change search only settings of existing fields. [source,js] -------------------------------------------------- PUT twitter <1> {} PUT twitter/\_mapping/\_doc <2> { "properties": { "email": { "type": "keyword" ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/put-mapping.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.015894770622253418,
0.054596152156591415,
0.04048582911491394,
0.0928441733121872,
-0.00031463097548112273,
0.02499573491513729,
0.029107434675097466,
0.03168589621782303,
0.07959309220314026,
-0.007670746184885502,
-0.012302189134061337,
0.002553563565015793,
0.02083095908164978,
-0.02... | 0.033968 |
[[indices-open-close]] == Open / Close Index API The open and close index APIs allow to close an index, and later on opening it. A closed index has almost no overhead on the cluster (except for maintaining its metadata), and is blocked for read/write operations. A closed index can be opened which will then go through t... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/open-close.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.010399366728961468,
0.015274186618626118,
-0.002646130509674549,
0.11249416321516037,
0.0632200762629509,
-0.024884244427084923,
-0.03724033012986183,
-0.006825575139373541,
0.10284964740276337,
-0.003509595524519682,
-0.028097253292798996,
0.06329558789730072,
-0.03704094514250755,
-0.... | 0.175262 |
[[indices-create-index]] == Create Index The create index API allows to instantiate an index. Elasticsearch provides support for multiple indices, including executing operations across several indices. [float] [[create-index-settings]] === Index Settings Each index created can have specific settings associated with it.... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/create-index.asciidoc | 6.2 | elasticsearch-6-2 | [
0.036087874323129654,
0.02355838008224964,
0.008638828992843628,
0.07831098884344101,
-0.013145091012120247,
0.0008606823976151645,
-0.0006197350448928773,
-0.0380534790456295,
0.0921844020485878,
0.0172417052090168,
-0.02190527506172657,
-0.045865498483181,
0.014293735846877098,
-0.015190... | 0.074445 |
PUT test?wait\_for\_active\_shards=2 -------------------------------------------------- // CONSOLE // TEST[skip:requires two nodes] A detailed explanation of `wait\_for\_active\_shards` and its possible values can be found <>. | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/create-index.asciidoc | 6.2 | elasticsearch-6-2 | [
0.026136305183172226,
-0.007777850609272718,
0.02234562486410141,
0.04974514618515968,
0.0498557910323143,
-0.05812028422951698,
-0.03324597328901291,
-0.09980848431587219,
0.05961243063211441,
0.020236380398273468,
0.0599762499332428,
-0.03543950989842415,
0.022627297788858414,
-0.0688750... | 0.031552 |
[[indices-shrink-index]] == Shrink Index The shrink index API allows you to shrink an existing index into a new index with fewer primary shards. The requested number of primary shards in the target index must be a factor of the number of shards in the source index. For example an index with `8` primary shards can be sh... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/shrink-index.asciidoc | 6.2 | elasticsearch-6-2 | [
0.004788750782608986,
0.04480047896504402,
0.06616225093603134,
0.06058263033628464,
0.06051578372716904,
-0.02485184371471405,
-0.055058810859918594,
0.014204412698745728,
0.05192846432328224,
0.023618564009666443,
-0.015402395278215408,
0.051404811441898346,
0.03642556816339493,
-0.00383... | 0.125275 |
for the target index: [source,js] -------------------------------------------------- POST my\_source\_index/\_shrink/my\_target\_index { "settings": { "index.number\_of\_replicas": 1, "index.number\_of\_shards": 1, <1> "index.codec": "best\_compression" <2> }, "aliases": { "my\_search\_indices": {} } } ----------------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/shrink-index.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.037053823471069336,
0.03726649284362793,
0.04112536832690239,
0.1002059206366539,
0.047156721353530884,
-0.00042544130701571703,
0.02259250544011593,
-0.029125967994332314,
0.05740465968847275,
-0.0026909385342150927,
-0.043895065784454346,
-0.014903257600963116,
0.03901490196585655,
-0... | 0.05724 |
[[indices-delete-index]] == Delete Index The delete index API allows to delete an existing index. [source,js] -------------------------------------------------- DELETE /twitter -------------------------------------------------- // CONSOLE // TEST[setup:twitter] The above example deletes an index called `twitter`. Speci... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/delete-index.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.03373054042458534,
0.05274354666471481,
0.0021461748983711004,
0.07239331305027008,
0.07067243754863739,
-0.03354283794760704,
0.08679402619600296,
-0.08089038729667664,
0.10669910162687302,
-0.025333493947982788,
-0.003002459416165948,
0.007815665565431118,
0.030208492651581764,
-0.009... | 0.080491 |
[[indices-get-settings]] == Get Settings The get settings API allows to retrieve settings of index/indices: [source,js] -------------------------------------------------- GET /twitter/\_settings -------------------------------------------------- // CONSOLE // TEST[setup:twitter] [float] === Multiple Indices and Types T... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/get-settings.asciidoc | 6.2 | elasticsearch-6-2 | [
0.025581875815987587,
0.05799973011016846,
-0.06707917153835297,
0.10802531242370605,
-0.008421733044087887,
-0.028747623786330223,
0.043873030692338943,
0.007244393229484558,
-0.003949265461415052,
-0.052864812314510345,
0.002297669416293502,
-0.04644137620925903,
0.014160677790641785,
-0... | 0.027122 |
[[indices-flush]] == Flush The flush API allows to flush one or more indices through an API. The flush process of an index basically frees memory from the index by flushing data to the index storage and clearing the internal <>. By default, Elasticsearch uses memory heuristics in order to automatically trigger flush op... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/flush.asciidoc | 6.2 | elasticsearch-6-2 | [
0.024906737729907036,
0.09330841153860092,
-0.0038695456460118294,
0.11064137518405914,
0.0006196543108671904,
-0.039849694818258286,
-0.01582697220146656,
-0.06959106028079987,
0.09433090686798096,
0.04310630261898041,
-0.005770071409642696,
0.017420051619410515,
0.009425626136362553,
-0.... | 0.096457 |
} } -------------------------------------------------- // TESTRESPONSE[s/"id" : "3M3zkw2GHMo2Y4h4\/KFKCg=="/"id": $body.indices.twitter.shards.0.0.commit.id/] // TESTRESPONSE[s/"translog\_uuid" : "hnOG3xFcTDeoI\_kvvvOdNA"/"translog\_uuid": $body.indices.twitter.shards.0.0.commit.user\_data.translog\_uuid/] // TESTRESPO... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/flush.asciidoc | 6.2 | elasticsearch-6-2 | [
0.03863145038485527,
0.03892828896641731,
-0.024250749498605728,
-0.007746613584458828,
0.08981427550315857,
-0.03333519399166107,
-0.008877787739038467,
-0.03459415212273598,
0.09113869071006775,
0.052419885993003845,
0.05754496902227402,
-0.06468507647514343,
0.01597294583916664,
0.00086... | -0.006323 |
[[indices-clearcache]] == Clear Cache The clear cache API allows to clear either all caches or specific cached associated with one or more indices. [source,js] -------------------------------------------------- POST /twitter/\_cache/clear -------------------------------------------------- // CONSOLE // TEST[setup:twitt... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/clearcache.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.011275584809482098,
0.08163117617368698,
-0.05737435817718506,
0.0696415901184082,
0.007133984472602606,
-0.08233007788658142,
0.08975440263748169,
-0.08726964890956879,
0.08737224340438843,
0.012711377814412117,
-0.013388521037995815,
0.02219194546341896,
-0.02069210819900036,
-0.04239... | 0.060982 |
[[indices-recovery]] == Indices Recovery The indices recovery API provides insight into on-going index shard recoveries. Recovery status may be reported for specific indices, or cluster-wide. For example, the following command would show recovery information for the indices "index1" and "index2". [source,js] ----------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/recovery.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.027066869661211967,
-0.011838351376354694,
-0.018395906314253807,
0.10347535461187363,
0.058973804116249084,
0.00399143947288394,
0.0018067467026412487,
-0.03675072640180588,
0.024377355352044106,
-0.050637200474739075,
0.020952627062797546,
0.013037674129009247,
-0.02354174666106701,
-... | 0.179315 |
: "10.0.1.7", "name" : "my\_es\_node" }, "index" : { "size" : { "total" : "24.7mb", "total\_in\_bytes" : 26001617, "reused" : "24.7mb", "reused\_in\_bytes" : 26001617, "recovered" : "0b", "recovered\_in\_bytes" : 0, "percent" : "100.0%" }, "files" : { "total" : 26, "reused" : 26, "recovered" : 0, "percent" : "100.0%", ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/recovery.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.05179043859243393,
0.05921517685055733,
0.014720884151756763,
0.05862322449684143,
0.03158022090792656,
-0.05782042816281319,
0.04454983398318291,
0.024888398125767708,
0.050841160118579865,
0.05644794553518295,
0.02447376772761345,
0.007982918061316013,
0.013947688974440098,
0.04741352... | 0.087539 |
[[indices-split-index]] == Split Index The split index API allows you to split an existing index into a new index, where each original primary shard is split into two or more primary shards in the new index. IMPORTANT: The `\_split` API requires the source index to be created with a specific `number\_of\_routing\_shard... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/split-index.asciidoc | 6.2 | elasticsearch-6-2 | [
0.028692074120044708,
-0.013607931323349476,
0.08956989645957947,
0.02734515257179737,
0.02968941628932953,
-0.0072068399749696255,
-0.07586152106523514,
-0.013650025241076946,
0.06515789777040482,
0.042604248970746994,
-0.05822430178523064,
0.00039282627403736115,
-0.013606972992420197,
-... | 0.066768 |
`settings` and `aliases` parameters for the target index: [source,js] -------------------------------------------------- POST my\_source\_index/\_split/my\_target\_index { "settings": { "index.number\_of\_shards": 5 <1> }, "aliases": { "my\_search\_indices": {} } } -------------------------------------------------- // ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/split-index.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.00979132205247879,
0.0345211885869503,
0.03845144435763359,
0.08165357261896133,
0.025955548509955406,
-0.016506681218743324,
0.03414610028266907,
-0.008143419399857521,
0.038200389593839645,
-0.03657796233892441,
-0.008183028548955917,
-0.01959981769323349,
0.020290909335017204,
-0.028... | 0.043406 |
[[indices-stats]] == Indices Stats Indices level stats provide statistics on different operations happening on an index. The API provides statistics on the index level scope (though most stats can also be retrieved using node level scope). The following returns high level aggregation and index level stats for all indic... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/stats.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04778109863400459,
0.010850919410586357,
-0.062767393887043,
0.12932747602462769,
0.02254526875913143,
-0.03069561906158924,
0.0015399755211547017,
0.03502344712615013,
0.07119478285312653,
-0.0065415995195508,
-0.056331243366003036,
-0.026458438485860825,
0.002751176944002509,
-0.04457... | 0.127089 |
[[indices-segments]] == Indices Segments Provide low level segments information that a Lucene index (shard level) is built with. Allows to be used to provide more information on the state of a shard and an index, possibly optimization information, data "wasted" on deletes, and so on. Endpoints include segments for a sp... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/segments.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.017095325514674187,
0.04676998406648636,
0.017226651310920715,
0.08054783195257187,
0.010013865306973457,
0.0025496482849121094,
0.008436180651187897,
-0.0208872240036726,
0.08563009649515152,
-0.055970948189496994,
-0.02710590325295925,
0.004691384732723236,
-0.008990947157144547,
-0.0... | 0.149485 |
... ] } ... } -------------------------------------------------- // NOTCONSOLE //Response is too verbose to be fully shown in documentation, so we just show the relevant bit and don't test the response. | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/segments.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04678066074848175,
0.02870331145823002,
-0.017843082547187805,
0.023559119552373886,
-0.022357765585184097,
-0.041565585881471634,
-0.0010749234352260828,
-0.01021723635494709,
0.008839160203933716,
-0.02276574820280075,
0.06031126528978348,
-0.07958955317735672,
0.056457873433828354,
-... | 0.088579 |
[[indices-shards-stores]] == Indices Shard Stores Provides store information for shard copies of indices. Store information reports on which nodes shard copies exist, the shard copy allocation ID, a unique identifier for each shard copy, and any exceptions encountered while opening the shard index or from earlier engin... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/shard-stores.asciidoc | 6.2 | elasticsearch-6-2 | [
0.0637139230966568,
0.00928907748311758,
-0.0431247279047966,
0.07411328703165054,
0.06904865801334381,
-0.002286426490172744,
0.005547049921005964,
-0.0511675663292408,
0.04865556210279465,
-0.048286277800798416,
0.018217923119664192,
0.025886576622724533,
0.015036900527775288,
-0.0291070... | 0.158492 |
[[indices-update-settings]] == Update Indices Settings Change specific index level settings in real time. The REST endpoint is `/\_settings` (to update all indices) or `{index}/\_settings` to update one (or more) indices settings. The body of the request includes the updated settings, for example: [source,js] ---------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/update-settings.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.010461041703820229,
0.039803195744752884,
-0.040697891265153885,
0.09108902513980865,
-0.029147563502192497,
0.008805663324892521,
-0.03243127465248108,
-0.03614543750882149,
0.035545751452445984,
0.009513246826827526,
0.008814777247607708,
-0.034962065517902374,
-0.006116519216448069,
... | 0.021121 |
[[indices-get-mapping]] == Get Mapping The get mapping API allows to retrieve mapping definitions for an index or index/type. [source,js] -------------------------------------------------- GET /twitter/\_mapping/\_doc -------------------------------------------------- // CONSOLE // TEST[setup:twitter] [float] === Multi... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/get-mapping.asciidoc | 6.2 | elasticsearch-6-2 | [
0.03711816668510437,
0.0547652393579483,
-0.0018196875462308526,
0.06264355778694153,
0.003167523769661784,
-0.04786704108119011,
0.05422467365860939,
0.008537516929209232,
0.02505687065422535,
-0.04055970534682274,
0.0008859310764819384,
-0.055779311805963516,
-0.003476593643426895,
0.015... | 0.062845 |
[[indices-templates]] == Index Templates Index templates allow you to define templates that will automatically be applied when new indices are created. The templates include both <> and <> and a simple pattern template that controls whether the template should be applied to the new index. NOTE: Templates are only appli... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/templates.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.03351890668272972,
0.05996240675449371,
0.07407066971063614,
0.05858774855732918,
-0.020761560648679733,
0.03127057105302811,
-0.03824629634618759,
-0.03376830741763115,
0.04372596740722656,
-0.03233939781785011,
-0.030500510707497597,
-0.002323409076780081,
-0.025146834552288055,
-0.02... | 0.070568 |
} } -------------------------------------------------- // CONSOLE // TEST[s/^/DELETE \_template\/template\_1\n/] The above will disable storing the `\_source`, but for indices that start with `te\*`, `\_source` will still be enabled. Note, for mappings, the merging is "deep", meaning that specific object/property based... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/templates.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.02849876880645752,
0.06289439648389816,
0.031198754906654358,
0.02063695713877678,
0.05573355406522751,
0.013317073695361614,
-0.02824411354959011,
-0.05790900066494942,
0.01968945562839508,
0.028658108785748482,
0.02081761322915554,
0.027255238965153694,
-0.05186472088098526,
-0.051263... | 0.030345 |
[[indices-forcemerge]] == Force Merge The force merge API allows to force merging of one or more indices through an API. The merge relates to the number of segments a Lucene index holds within each shard. The force merge operation allows to reduce the number of segments by merging them. This call will block until the m... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/indices/forcemerge.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.038804758340120316,
0.030391501262784004,
-0.025990581139922142,
0.08375921100378036,
0.007593690883368254,
-0.050783704966306686,
0.0004152797337155789,
-0.026661526411771774,
0.09348884969949722,
-0.03610054403543472,
0.017178155481815338,
-0.010828778147697449,
-0.013373596593737602,
... | 0.069246 |
[[analysis-analyzers]] == Analyzers Elasticsearch ships with a wide range of built-in analyzers, which can be used in any index without further configuration: <>:: The `standard` analyzer divides text into terms on word boundaries, as defined by the Unicode Text Segmentation algorithm. It removes most punctuation, lowe... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.006157864350825548,
0.08510196208953857,
0.01928749680519104,
0.00908777117729187,
0.041987281292676926,
-0.07179692387580872,
-0.003571218578144908,
-0.0476275198161602,
0.01661061681807041,
0.0048619345761835575,
0.029893383383750916,
0.041505783796310425,
0.01661447063088417,
0.04833... | 0.189189 |
[[analysis-normalizers]] == Normalizers beta[] Normalizers are similar to analyzers except that they may only emit a single token. As a consequence, they do not have a tokenizer and only accept a subset of the available char filters and token filters. Only the filters that work on a per-character basis are allowed. For... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/normalizers.asciidoc | 6.2 | elasticsearch-6-2 | [
0.029444100335240364,
-0.007899889722466469,
0.008678684011101723,
0.01896103285253048,
-0.014763491228222847,
0.034641508013010025,
-0.028468988835811615,
-0.02841467782855034,
-0.06985494494438171,
-0.006860077381134033,
-0.008120391517877579,
-0.07053054869174957,
-0.00013787366333417594,... | 0.128659 |
== Testing analyzers The <> is an invaluable tool for viewing the terms produced by an analyzer. A built-in analyzer (or combination of built-in tokenizer, token filters, and character filters) can be specified inline in the request: [source,js] ------------------------------------- POST \_analyze { "analyzer": "whites... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/testing.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.05593091621994972,
0.07561999559402466,
-0.014516809023916721,
0.07581605017185211,
0.02926466055214405,
0.002960619516670704,
0.03853648528456688,
-0.04416551813483238,
0.07492885738611221,
-0.030306069180369377,
-0.039549026638269424,
-0.02995998039841652,
0.012906468473374844,
0.0144... | 0.099771 |
[[analysis-charfilters]] == Character Filters \_Character filters\_ are used to preprocess the stream of characters before it is passed to the <>. A character filter receives the original text as a stream of characters and can transform the stream by adding, removing, or changing characters. For instance, a character f... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/charfilters.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.025223828852176666,
0.0630669966340065,
0.0157312098890543,
0.015105470083653927,
-0.003981983754783869,
-0.0010413042036816478,
0.003808016423135996,
-0.10357645899057388,
0.07088764011859894,
-0.04372099041938782,
0.006069918628782034,
-0.03296943008899689,
0.04246353730559349,
0.0001... | 0.128983 |
[[analyzer-anatomy]] == Anatomy of an analyzer An \_analyzer\_ -- whether built-in or custom -- is just a package which contains three lower-level building blocks: \_character filters\_, \_tokenizers\_, and \_token filters\_. The built-in <> pre-package these building blocks into analyzers suitable for different langua... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/anatomy.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.03813156485557556,
0.08227363973855972,
0.012373683974146843,
0.030655251815915108,
-0.0031980217900127172,
-0.046336181461811066,
0.007729006465524435,
-0.07975758612155914,
0.0623055174946785,
-0.004707567859441042,
-0.020388219505548477,
-0.06605181097984314,
0.027147933840751648,
0.... | 0.19667 |
[[analysis-tokenfilters]] == Token Filters Token filters accept a stream of tokens from a <> and can modify tokens (eg lowercasing), delete tokens (eg remove stopwords) or add tokens (eg synonyms). Elasticsearch has a number of built in token filters which can be used to build <>. include::tokenfilters/standard-tokenfi... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/tokenfilters.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.029401374980807304,
0.04364268109202385,
0.03395528718829155,
0.015549949370324612,
0.024319328367710114,
-0.017749518156051636,
0.0009357636445201933,
-0.02810409665107727,
0.012299355119466782,
-0.0021417727693915367,
-0.039370566606521606,
-0.07046866416931152,
0.02586924284696579,
0... | 0.130457 |
[[analysis-tokenizers]] == Tokenizers A \_tokenizer\_ receives a stream of characters, breaks it up into individual \_tokens\_ (usually individual words), and outputs a stream of \_tokens\_. For instance, a <> tokenizer breaks text into tokens whenever it sees any whitespace. It would convert the text `"Quick brown fox... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/tokenizers.asciidoc | 6.2 | elasticsearch-6-2 | [
0.00718062836676836,
0.03203515708446503,
0.014804460108280182,
0.055318187922239304,
0.04481305554509163,
-0.028530625626444817,
0.04319198057055473,
-0.020862692967057228,
0.06673342734575272,
-0.010258154943585396,
-0.004579640459269285,
0.01027383841574192,
0.03532383218407631,
-0.0013... | 0.205295 |
tree, e.g. `/foo/bar/baz` -> `[/foo, /foo/bar, /foo/bar/baz ]`. include::tokenizers/standard-tokenizer.asciidoc[] include::tokenizers/letter-tokenizer.asciidoc[] include::tokenizers/lowercase-tokenizer.asciidoc[] include::tokenizers/whitespace-tokenizer.asciidoc[] include::tokenizers/uaxurlemail-tokenizer.asciidoc[] in... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/tokenizers.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.047413237392902374,
-0.01761334016919136,
0.05060109123587608,
0.028983889147639275,
-0.014801071025431156,
-0.011153074912726879,
0.01963791251182556,
-0.007955847308039665,
-0.024057015776634216,
-0.056790176779031754,
0.07748961448669434,
-0.03691418468952179,
0.03187765181064606,
0.... | 0.049317 |
[[analysis-standard-analyzer]] === Standard Analyzer The `standard` analyzer is the default analyzer which is used if none is specified. It provides grammar based tokenization (based on the Unicode Text Segmentation algorithm, as specified in http://unicode.org/reports/tr29/[Unicode Standard Annex #29]) and works well ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/standard-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04087652266025543,
0.08755016326904297,
-0.053465548902750015,
0.06141458451747894,
0.005941079929471016,
-0.03524785861372948,
0.01745024137198925,
0.006531926337629557,
0.032663922756910324,
-0.050204481929540634,
-0.009293428622186184,
-0.07802458852529526,
-0.01824997551739216,
0.09... | 0.154069 |
brown, foxes, jumpe, d, over, lazy, dog's, bone ] --------------------------- | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/standard-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
0.003934048116207123,
-0.07070033997297287,
0.08271383494138718,
0.017258737236261368,
-0.05085418373346329,
-0.015534129925072193,
0.05694108456373215,
-0.0903090387582779,
-0.015207490883767605,
0.08866364508867264,
0.07170987874269485,
-0.04866405948996544,
0.003059210954234004,
0.01606... | -0.025759 |
[[analysis-stop-analyzer]] === Stop Analyzer The `stop` analyzer is the same as the <> but adds support for removing stop words. It defaults to using the `\_english\_` stop words. [float] === Definition It consists of: Tokenizer:: \* <> Token filters:: \* <> [float] === Example output [source,js] ----------------------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/stop-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04968618229031563,
0.08487023413181305,
0.022472983226180077,
0.03869256004691124,
0.05633766949176788,
0.01615232229232788,
0.05457952991127968,
-0.08232498168945312,
0.06489434838294983,
-0.035288579761981964,
0.0077418615110218525,
-0.02315845899283886,
-0.037114061415195465,
0.00880... | 0.139755 |
[[analysis-pattern-analyzer]] === Pattern Analyzer The `pattern` analyzer uses a regular expression to split the text into terms. The regular expression should match the \*token separators\* not the tokens themselves. The regular expression defaults to `\W+` (or all non-word characters). [WARNING] .Beware of Pathologic... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/pattern-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.08128064125776291,
0.06096469983458519,
0.056185346096754074,
-0.0019796283449977636,
0.021743562072515488,
-0.04936954379081726,
-0.031197618693113327,
-0.008139943704009056,
-0.01722426526248455,
0.025576982647180557,
-0.017653515562415123,
-0.03794340416789055,
0.026399608701467514,
... | 0.120077 |
example produces the following terms: [source,text] --------------------------- [ john, smith, foo, bar, com ] --------------------------- [float] ==== CamelCase tokenizer The following more complicated example splits CamelCase text into tokens: [source,js] -------------------------------------------------- PUT my\_ind... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/pattern-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04544936120510101,
0.08630022406578064,
0.09003924578428268,
0.045266326516866684,
0.005307372193783522,
-0.007141903508454561,
0.04959343746304512,
-0.030369969084858894,
0.05255735293030739,
-0.014703169465065002,
-0.023299643769860268,
-0.027068430557847023,
0.028518831357359886,
0.0... | 0.060464 |
[[analysis-fingerprint-analyzer]] === Fingerprint Analyzer The `fingerprint` analyzer implements a https://github.com/OpenRefine/OpenRefine/wiki/Clustering-In-Depth#fingerprint[fingerprinting algorithm] which is used by the OpenRefine project to assist in clustering. Input text is lowercased, normalized to remove exten... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/fingerprint-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.08847849816083908,
0.09243354946374893,
-0.037973638623952866,
0.026834819465875626,
0.05231524258852005,
-0.0020984970033168793,
0.09859567880630493,
-0.04682532325387001,
-0.019296076148748398,
-0.08613798022270203,
0.07761264592409134,
-0.002427197527140379,
0.051449164748191833,
-0.... | 0.168384 |
[[analysis-lang-analyzer]] === Language Analyzers A set of analyzers aimed at analyzing specific language text. The following types are supported: <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>. ==== Configuring language analyzers =... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/lang-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
0.0006753343623131514,
0.05567687749862671,
-0.018241411074995995,
-0.011442529037594795,
0.0014410509029403329,
0.034674592316150665,
0.0712718591094017,
0.009634045884013176,
-0.08076968044042587,
0.0007325821788981557,
0.0666748657822609,
-0.048738762736320496,
0.07348040491342545,
0.02... | 0.139554 |
{ "type": "stop", "stopwords": "\_bengali\_" <1> }, "bengali\_keywords": { "type": "keyword\_marker", "keywords": ["উদাহরণ"] <2> }, "bengali\_stemmer": { "type": "stemmer", "language": "bengali" } }, "analyzer": { "bengali": { "tokenizer": "standard", "filter": [ "lowercase", "indic\_normalization", "bengali\_normaliza... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/lang-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
0.01830054074525833,
0.06384442746639252,
-0.016477016732096672,
0.025471972301602364,
-0.03379419445991516,
0.06966492533683777,
0.03541664779186249,
-0.0489870123565197,
-0.06296034157276154,
-0.008656932041049004,
-0.004842156544327736,
-0.05667353793978691,
-0.013822517357766628,
0.033... | 0.066935 |
should be removed unless there are words which should be excluded from stemming. [[danish-analyzer]] ===== `danish` analyzer The `danish` analyzer could be reimplemented as a `custom` analyzer as follows: [source,js] ---------------------------------------------------- PUT /danish\_example { "settings": { "analysis": {... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/lang-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04355096071958542,
0.1254245638847351,
0.05323879048228264,
0.043079011142253876,
0.031680066138505936,
0.04777603968977928,
-0.0043080649338662624,
-0.048096273094415665,
0.021083276718854904,
-0.010881021618843079,
0.005515013821423054,
-0.045534443110227585,
-0.017875049263238907,
0.... | 0.017425 |
should be removed unless there are words which should be excluded from stemming. [[galician-analyzer]] ===== `galician` analyzer The `galician` analyzer could be reimplemented as a `custom` analyzer as follows: [source,js] ---------------------------------------------------- PUT /galician\_example { "settings": { "anal... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/lang-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.031108209863305092,
0.09337183088064194,
0.029066219925880432,
0.05705931410193443,
0.04344978183507919,
0.031110353767871857,
-0.014176455326378345,
-0.049778178334236145,
-0.00809457991272211,
-0.05136870592832565,
0.0292224008589983,
-0.019212352111935616,
-0.06940332800149918,
0.046... | 0.050671 |
{ "analysis": { "filter": { "indonesian\_stop": { "type": "stop", "stopwords": "\_indonesian\_" <1> }, "indonesian\_keywords": { "type": "keyword\_marker", "keywords": ["contoh"] <2> }, "indonesian\_stemmer": { "type": "stemmer", "language": "indonesian" } }, "analyzer": { "indonesian": { "tokenizer": "standard", "filt... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/lang-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
0.007989980280399323,
0.08179157972335815,
0.04405493661761284,
0.024709438905119896,
0.0029827661346644163,
0.020956339314579964,
0.04214686155319214,
-0.02872735820710659,
-0.02898077294230461,
0.012980792671442032,
0.002273778198286891,
-0.07296621054410934,
-0.05023842304944992,
0.0280... | 0.0565 |
PUT /norwegian\_example { "settings": { "analysis": { "filter": { "norwegian\_stop": { "type": "stop", "stopwords": "\_norwegian\_" <1> }, "norwegian\_keywords": { "type": "keyword\_marker", "keywords": ["eksempel"] <2> }, "norwegian\_stemmer": { "type": "stemmer", "language": "norwegian" } }, "analyzer": { "norwegian"... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/lang-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.008817424066364765,
0.09791151434183121,
0.06548462063074112,
0.005650326609611511,
0.020715225487947464,
0.02247012034058571,
0.01576911099255085,
0.004291422199457884,
-0.03900833800435066,
0.023729341104626656,
-0.010258749127388,
-0.06783724576234818,
-0.028826558962464333,
0.026693... | 0.029635 |
} ---------------------------------------------------- // CONSOLE <1> The default stopwords can be overridden with the `stopwords` or `stopwords\_path` parameters. <2> This filter should be removed unless there are words which should be excluded from stemming. [[spanish-analyzer]] ===== `spanish` analyzer The `spanish`... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/lang-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.02303110994398594,
0.054249491542577744,
0.014080322347581387,
0.055930301547050476,
0.03065957874059677,
0.05744413286447525,
0.02330124005675316,
-0.0640714168548584,
-0.016269613057374954,
-0.04255090281367302,
0.00015385301958303899,
-0.0517144612967968,
-0.027640769258141518,
0.057... | 0.069044 |
[[analysis-simple-analyzer]] === Simple Analyzer The `simple` analyzer breaks text into terms whenever it encounters a character which is not a letter. All terms are lower cased. [float] === Definition It consists of: Tokenizer:: \* <> [float] === Example output [source,js] --------------------------- POST \_analyze { ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/simple-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04584032669663429,
0.08582820743322372,
0.010837935842573643,
0.06970593333244324,
-0.0011629521613940597,
-0.015480488538742065,
0.026385601609945297,
-0.020034173503518105,
0.05879157781600952,
-0.025800785049796104,
0.01722339168190956,
-0.06254938244819641,
-0.0008078899118117988,
0... | 0.108648 |
[[analysis-keyword-analyzer]] === Keyword Analyzer The `keyword` analyzer is a ``noop'' analyzer which returns the entire input string as a single token. [float] === Definition It consists of: Tokenizer:: \* <> [float] === Example output [source,js] --------------------------- POST \_analyze { "analyzer": "keyword", "t... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/keyword-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.03333183005452156,
0.09934663772583008,
-0.02057567797601223,
0.060178011655807495,
0.0075040655210614204,
-0.04192255809903145,
0.08384691923856735,
-0.007167999166995287,
0.059447988867759705,
-0.03965626284480095,
0.018884390592575073,
-0.06039562076330185,
0.0023862007074058056,
0.0... | 0.128569 |
[[configuring-analyzers]] === Configuring built-in analyzers The built-in analyzers can be used directly without any configuration. Some of them, however, support configuration options to alter their behaviour. For instance, the <> can be configured to support a list of stop words: [source,js] -------------------------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/configuring.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.02801491878926754,
0.06717044860124588,
0.003949558828026056,
0.04145098105072975,
0.006485069636255503,
0.02695007063448429,
0.011195182800292969,
-0.03116934560239315,
-0.016945265233516693,
-0.014938784763216972,
-0.02078143320977688,
-0.01491762138903141,
0.029177850112318993,
0.031... | 0.056545 |
[[analysis-custom-analyzer]] === Custom Analyzer When the built-in analyzers do not fulfill your needs, you can create a `custom` analyzer which uses the appropriate combination of: \* zero or more <> \* a <> \* zero or more <>. [float] === Configuration The `custom` analyzer accepts the following parameters: [horizont... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/analysis/analyzers/custom-analyzer.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.022150369361042976,
0.11167510598897934,
-0.025392498821020126,
0.019998280331492424,
0.0019499650225043297,
0.0285653006285429,
0.03803084418177605,
-0.056305211037397385,
0.03357604146003723,
0.015730416402220726,
0.008379723876714706,
-0.1201007142663002,
0.04549083486199379,
0.03291... | 0.080085 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.