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 |
|---|---|---|---|---|---|
text is a difficult task at index-time but we can cleanse the data on-the-fly at query time using the `filter\_duplicate\_text` setting. First let's look at an unfiltered real-world example using the http://research.signalmedia.co/newsir16/signal-dataset.html[Signal media dataset] of a million news articles covering a ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.01329145859926939,
0.05268863961100578,
0.051635775715112686,
0.10915963351726532,
0.03933509811758995,
0.022763175889849663,
0.02544318698346615,
-0.06460744887590408,
0.09314173460006714,
-0.01739884354174137,
-0.009878229349851608,
0.022581620141863823,
0.024782389402389526,
-0.00407... | 0.056371 |
a consequence of copy-and-paste operations or other forms of mechanical repetition. If your duplicate or near-duplicate content is identifiable via a single-value indexed field (perhaps a hash of the article's `title` text or an `original\_press\_release\_url` field) then it would be more efficient to use a parent <> a... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.020841090008616447,
0.017070164903998375,
0.01870807074010372,
0.06072818860411644,
0.010851763188838959,
0.05579855665564537,
-0.008910518139600754,
0.11107679456472397,
0.13663350045681,
-0.01752946339547634,
-0.015383478254079819,
0.04527590423822403,
0.08997902274131775,
-0.06255324... | 0.09398 |
we have chosen to provide fast performance at the cost of some (typically small) inaccuracies. However, the `size` and `shard size` settings covered in the next section provide tools to help control the accuracy levels. ==== Parameters ===== Significance heuristics This aggregation supports the same scoring heuristics ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.026366494596004486,
-0.017536986619234085,
0.01335033867508173,
0.03876882046461105,
-0.03219117224216461,
-0.02817070670425892,
-0.03803837299346924,
0.006212200503796339,
0.06326737999916077,
-0.028623264282941818,
-0.0362992063164711,
-0.00925331562757492,
0.08462540805339813,
-0.0414... | 0.021913 |
this increases memory consumption and network traffic. `shard\_min\_doc\_count` parameter The parameter `shard\_min\_doc\_count` regulates the \_certainty\_ a shard has if the term should actually be added to the candidate list or not with respect to the `min\_doc\_count`. Terms will only be considered if their local s... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/significanttext-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.06923729181289673,
-0.037379808723926544,
-0.003105507930740714,
-0.0023837131448090076,
-0.02680637128651142,
0.007636316120624542,
0.041662704199552536,
-0.009688835591077805,
0.05693493410944939,
-0.03200683742761612,
0.06258077919483185,
-0.008868003264069557,
0.0978408083319664,
-0.... | 0.047227 |
[[search-aggregations-bucket-datehistogram-aggregation]] === Date Histogram Aggregation A multi-bucket aggregation similar to the <> except it can only be applied on date values. Since dates are represented in Elasticsearch internally as long values, it is possible to use the normal `histogram` on dates as well, though... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.0025771469809114933,
0.06731588393449783,
0.027622165158391,
0.008443188853561878,
-0.055732645094394684,
0.056585054844617844,
-0.07667891681194305,
0.01804043911397457,
0.03208694979548454,
-0.02766823209822178,
-0.05376449227333069,
-0.025140807032585144,
0.012544773519039154,
-0.0126... | 0.079746 |
2015: [source,js] --------------------------------- { ... "aggregations": { "by\_day": { "buckets": [ { "key\_as\_string": "2015-10-01T00:00:00.000Z", "key": 1443657600000, "doc\_count": 2 } ] } } } --------------------------------- // TESTRESPONSE[s/\.\.\./"took": $body.took,"timed\_out": false,"\_shards": $body.\_sha... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.01512200478464365,
0.07869046181440353,
0.038269054144620895,
0.06163985654711723,
0.03471275046467781,
-0.05377522110939026,
-0.007965410128235817,
-0.01764838397502899,
0.13087911903858185,
0.01888945885002613,
-0.0227079875767231,
-0.06202593073248863,
-0.0075290207751095295,
-0.0241... | 0.017428 |
} } } -------------------------------------------------- // TESTRESPONSE[s/\.\.\./"took": $body.took,"timed\_out": false,"\_shards": $body.\_shards,"hits": $body.hits,/] ==== Scripts Like with the normal <>, both document level scripts and value level scripts are supported. It is also possible to control the order of t... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/datehistogram-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.037738971412181854,
0.051566679030656815,
0.05333374813199043,
0.03234373778104782,
0.022563958540558815,
-0.008366641588509083,
-0.024585021659731865,
-0.014247381128370762,
0.07783132046461105,
0.03213978931307793,
-0.007622923702001572,
0.0170111283659935,
0.058810021728277206,
-0.043... | -0.026881 |
[[search-aggregations-bucket-terms-aggregation]] === Terms Aggregation A multi-bucket value source based aggregation where buckets are dynamically built - one per unique value. ////////////////////////// [source,js] -------------------------------------------------- PUT /products { "mappings": { "product": { "propertie... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/terms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.030962390825152397,
-0.009575093165040016,
0.030849514529109,
0.03779393807053566,
-0.03763092681765556,
0.08634301275014877,
0.03213964030146599,
-0.015493674203753471,
0.0694078877568245,
-0.04558572918176651,
-0.023325329646468163,
-0.03662420064210892,
0.03510002791881561,
-0.020770... | -0.018337 |
{ "products" : { "terms" : { "field" : "product", "size" : 5 } } } } -------------------------------------------------- // CONSOLE // TEST[s/\_search/\_search\?filter\_path=aggregations/] The terms for each of the three shards are shown below with their respective document counts in brackets: [width="100%",cols="^2,^2,... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/terms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.02464800328016281,
0.0064568109810352325,
-0.001553565845824778,
0.003981953486800194,
-0.0013147062854841352,
0.024974022060632706,
-0.008971272967755795,
-0.051503486931324005,
0.06517147272825241,
-0.02745121344923973,
-0.010007108561694622,
-0.03058384731411934,
0.062300268560647964,
... | 0.019315 |
to bigger data transfers between the nodes and the client). The `shard\_size` parameter can be used to minimize the extra work that comes with bigger requested `size`. When defined, it will determine how many terms the coordinating node will request from each shard. Once all the shards responded, the coordinating node ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/terms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.05666496232151985,
0.03389041870832443,
0.05927470326423645,
0.052515801042318344,
0.01812930591404438,
-0.020230159163475037,
-0.06802767515182495,
0.016645604744553566,
0.08113402128219604,
0.05102162808179855,
-0.061043474823236465,
0.02626916579902172,
0.07627587020397186,
-0.0495789... | 0.016774 |
... ] } } } -------------------------------------------------- // TESTRESPONSE[s/\.\.\.//] // TESTRESPONSE[s/: (\-)?[0-9]+/: $body.$\_path/] These errors can only be calculated in this way when the terms are ordered by descending document count. When the aggregation is ordered by the terms values themselves (either asc... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/terms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.008017883636057377,
0.009949413128197193,
0.045000918209552765,
0.07177245616912842,
-0.03623747080564499,
0.04145657643675804,
-0.011631515808403492,
0.020245512947440147,
0.10528009384870529,
0.022846709936857224,
0.009585939347743988,
-0.02071080356836319,
0.11254213005304337,
-0.043... | -0.039214 |
of docs in the bucket (i.e. `doc\_count`), in case it's a metrics one, the same rules as above apply (where the path must indicate the metric name to sort by in case of a multi-value metrics aggregation, and in case of a single-value metrics aggregation the sort will be applied on that value). The path must be defined ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/terms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.03603440150618553,
-0.021076953038573265,
0.02868644893169403,
0.014851485379040241,
-0.08461063355207443,
0.035158030688762665,
-0.03743436187505722,
0.04689192771911621,
0.1070137470960617,
0.03469111770391464,
-0.03309140354394913,
-0.024304907768964767,
0.029713090509176254,
-0.0471... | 0.036296 |
shard has if the term should actually be added to the candidate list or not with respect to the `min\_doc\_count`. Terms will only be considered if their local shard frequency within the set is higher than the `shard\_min\_doc\_count`. If your dictionary contains many low frequent terms and you are not interested in th... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/terms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.03829329460859299,
-0.032586947083473206,
0.009720309637486935,
-0.0016567102866247296,
-0.01685156673192978,
0.046333737671375275,
0.002189263701438904,
-0.02674943022429943,
0.0828196331858635,
-0.018154866993427277,
0.07848741114139557,
-0.034745365381240845,
0.09990889579057693,
-0.0... | -0.049377 |
values For matching based on exact values the `include` and `exclude` parameters can simply take an array of strings that represent the terms as they are found in the index: [source,js] -------------------------------------------------- GET /\_search { "aggs" : { "JapaneseCars" : { "terms" : { "field" : "make", "includ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/terms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04467075690627098,
0.06930942833423615,
0.04980789124965668,
0.0343022458255291,
0.043248433619737625,
0.009643428027629852,
0.06578496843576431,
-0.02678901143372059,
0.04888877272605896,
-0.06132311746478081,
0.02446236088871956,
-0.029112447053194046,
0.0034348671324551105,
-0.011677... | 0.024786 |
which would not be possible across multiple fields. There are two approaches that you can use to perform a `terms` agg across multiple fields: <>:: Use a script to retrieve terms from multiple fields. This disables the global ordinals optimization and will be slower than collecting terms from a single field, but it giv... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/terms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.002407190389931202,
-0.020937621593475342,
-0.012668263167142868,
-0.01810166984796524,
0.0013208806049078703,
0.010057542473077774,
-0.02341487817466259,
-0.015932206064462662,
0.07041424512863159,
0.0019197120564058423,
0.006100850645452738,
-0.02194221504032612,
0.04929293692111969,
0... | 0.014624 |
the query on the second pass but only for the documents belonging to the top buckets. [[search-aggregations-bucket-terms-aggregation-execution-hint]] ==== Execution hint There are different mechanisms by which terms aggregations can be executed: - by using field values directly in order to aggregate data per-bucket (`m... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/terms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.05980519950389862,
0.039369963109493256,
0.030591348186135292,
0.048330169171094894,
0.012109429575502872,
0.03457397595047951,
-0.03440074622631073,
0.038957659155130386,
0.1075737401843071,
0.03753814473748207,
-0.027518386021256447,
0.007802023086696863,
0.028792941942811012,
-0.05548... | 0.02643 |
[[search-aggregations-bucket-adjacency-matrix-aggregation]] === Adjacency Matrix Aggregation A bucket aggregation returning a form of https://en.wikipedia.org/wiki/Adjacency\_matrix[adjacency matrix]. The request provides a collection of named filter expressions, similar to the `filters` aggregation request. Each bucke... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/adjacency-matrix-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.07317989319562912,
0.012919997796416283,
-0.06675072759389877,
0.046893101185560226,
-0.03305237367749214,
0.004415079485625029,
-0.05222656950354576,
-0.08758184313774109,
0.040775030851364136,
-0.03723147511482239,
-0.0032164594158530235,
-0.05943216755986214,
0.009925726801156998,
0.... | 0.084438 |
[[search-aggregations-bucket-composite-aggregation]] === Composite Aggregation beta[] A multi-bucket aggregation that creates composite buckets from different sources. Unlike the other `multi-bucket` aggregation the `composite` aggregation can be used to paginate \*\*all\*\* buckets from a multi-level aggregation effic... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/composite-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04729585349559784,
0.03937467560172081,
0.0088705038651824,
0.01864040270447731,
-0.021892376244068146,
0.05793512240052223,
-0.04902488365769386,
0.013489298522472382,
0.08170781284570694,
-0.00631316052749753,
-0.0685286745429039,
0.030567526817321777,
0.058960724622011185,
0.00655597... | 0.045501 |
} -------------------------------------------------- // CONSOLE ===== Date Histogram The `date\_histogram` is similar to the `histogram` value source except that the interval is specified by date/time expression: [source,js] -------------------------------------------------- GET /\_search { "aggs" : { "my\_buckets": { ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/composite-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.021440399810671806,
0.08427228778600693,
0.041016653180122375,
0.022807639092206955,
-0.019464414566755295,
0.04627428948879242,
-0.03458082303404808,
0.029926251620054245,
0.014849869534373283,
-0.03500819578766823,
-0.06824278831481934,
-0.07697741687297821,
0.009462058544158936,
-0.06... | 0.01597 |
-------------------------------------------------- // CONSOLE \... will sort the composite bucket in descending order when comparing values from the `date\_histogram` source and in ascending order when comparing values from the `terms` source. ==== Size The `size` parameter can be set to define how many composite bucke... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/composite-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.008193888701498508,
0.03358267992734909,
0.0215455312281847,
0.007913900539278984,
-0.0190719123929739,
-0.010521960444748402,
-0.03974442556500435,
0.05242346599698067,
-0.0020334755536168814,
0.04158753529191017,
-0.0757148414850235,
-0.009642397053539753,
0.07030226290225983,
-0.04010... | -0.006006 |
{ "date": 1494374400000, "product": "mad max" }, "doc\_count": 1, "the\_avg": { "value": 27.0 } }, { "key": { "date": 1494288000000, "product" : "mad max" }, "doc\_count": 2, "the\_avg": { "value": 22.5 } }, { "key": { "date": 1494201600000, "product": "rocky" }, "doc\_count": 1, "the\_avg": { "value": 10.0 } } ] } } }... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/composite-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.026761304587125778,
0.07083512842655182,
0.0197194404900074,
0.08691805601119995,
-0.016329219564795494,
0.023891737684607506,
0.014349382370710373,
0.0712064728140831,
0.059926752001047134,
0.023593619465827942,
0.030918819829821587,
0.026351576671004295,
0.012930640950798988,
-0.02413... | -0.005584 |
[[search-aggregations-bucket-missing-aggregation]] === Missing Aggregation A field data based single bucket aggregation, that creates a bucket of all documents in the current document set context that are missing a field value (effectively, missing a field or having the configured NULL value set). This aggregator will ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/missing-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.048478201031684875,
0.10432149469852448,
-0.0236501507461071,
0.10628566890954971,
0.0018828025786206126,
0.06999319791793823,
-0.04345681890845299,
0.04572479426860809,
0.1078132912516594,
-0.07099676877260208,
0.014364387840032578,
-0.04553188756108284,
0.06289234012365341,
-0.0678187... | 0.008421 |
[[search-aggregations-bucket-significantterms-aggregation]] === Significant Terms Aggregation An aggregation that returns interesting or unusual occurrences of terms in a set. .Example use cases: \* Suggesting "H5N1" when users search for "bird flu" in text \* Identifying the merchant that is the "common point of compr... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.023174332454800606,
0.053463563323020935,
0.03272238001227379,
0.03767755255103111,
0.033414795994758606,
0.040137529373168945,
0.04972917586565018,
0.09625685960054398,
0.06718788295984268,
-0.0148722929880023,
-0.0023322212509810925,
-0.013320043683052063,
0.054787423461675644,
-0.0222... | 0.103501 |
use a parent-level aggregation to segment the data ready for analysis. Example using a parent aggregation for segmentation: [source,js] -------------------------------------------------- GET /\_search { "aggregations": { "forces": { "terms": {"field": "force"}, "aggregations": { "significant\_crime\_types": { "signific... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.004701605532318354,
0.04351494088768959,
0.008749679662287235,
0.0521242581307888,
0.056878745555877686,
0.02702968195080757,
0.006086288020014763,
0.05225099250674248,
0.06306847929954529,
-0.03598529472947121,
-0.0034365172032266855,
-0.04574694484472275,
-0.051482800394296646,
0.02438... | 0.022262 |
a useful `boost` setting to sort matches. Using the `minimum\_should\_match` setting of the `terms` query with the keywords will help control the balance of precision/recall in the result set i.e a high setting would have a small number of relevant results packed full of keywords and a setting of "1" would produce a mo... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.035045210272073746,
0.020203927531838417,
0.009371938183903694,
0.025984451174736023,
0.05292097479104996,
0.03693559393286705,
0.09956604987382889,
0.0654892772436142,
-0.0032981489785015583,
0.03408076614141464,
0.01910877227783203,
-0.04229319468140602,
0.07596203684806824,
-0.006607... | 0.014212 |
of RAM to embed large child aggregations under a significant\_terms aggregation that later discards many candidate terms. It is advisable in these cases to perform two searches - the first to provide a rationalized list of significant\_terms and then add this shortlist of terms to a second query to go back and fetch th... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.02433312125504017,
0.00034388439962640405,
-0.01670234464108944,
0.061722926795482635,
0.012419388629496098,
0.021013591438531876,
-0.04198833554983139,
0.016991883516311646,
0.07087648659944534,
-0.018841702491044998,
-0.02476370520889759,
0.015889756381511688,
0.09090391546487808,
-0.0... | 0.053079 |
this heuristic to select the rarest terms such as typos that occur only once because they score 1/1 = 100%. It would be hard for a seasoned boxer to win a championship if the prize was awarded purely on the basis of percentage of fights won - by these rules a newcomer with only one fight under his belt would be impossi... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.019273806363344193,
0.04117000102996826,
-0.03941221162676811,
0.002082843566313386,
-0.005502977874130011,
0.11011529713869095,
0.08852739632129669,
0.043749067932367325,
0.11653266847133636,
0.031474050134420395,
0.0013137571513652802,
-0.08899001032114029,
0.0772332102060318,
0.034423... | 0.024729 |
be the most interesting ones once all results are combined so the significant\_terms aggregation can produce higher-quality results when the `shard\_size` parameter is set to values significantly higher than the `size` setting. This ensures that a bigger volume of promising candidate terms are given a consolidated revi... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.03058513253927231,
0.012195245362818241,
0.04269558936357498,
0.05483695864677429,
0.029457319527864456,
-0.003474415745586157,
-0.07941152900457382,
0.014084958471357822,
0.0824090912938118,
0.045605044811964035,
-0.048044510185718536,
0.013485867530107498,
0.07931797206401825,
-0.02649... | 0.035916 |
shard level. This value should be set much lower than `min\_doc\_count/#shards`. ===== Custom background context The default source of statistical information for background term frequencies is the entire index and this scope can be narrowed through the use of a `background\_filter` to focus in on significant terms wit... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/significantterms-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.07000354677438736,
0.07214047014713287,
0.04249288886785507,
0.05475196987390518,
0.05937085300683975,
-0.005415983032435179,
-0.02648269571363926,
0.008144903928041458,
0.09088745713233948,
-0.04970219358801842,
-0.02517668902873993,
-0.07663466781377792,
0.006238908041268587,
-0.024506... | 0.009948 |
[[search-aggregations-bucket-children-aggregation]] === Children Aggregation A special single bucket aggregation that selects child documents that have the specified type, as defined in a <>. This aggregation has a single option: \* `type` - The child type that should be selected. For example, let's say we have an inde... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/children-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.030363889411091805,
0.06505980342626572,
0.08086178451776505,
0.11632204800844193,
-0.013344386592507362,
0.0394650436937809,
0.007738916203379631,
0.036765336990356445,
0.08073987066745758,
-0.02597776986658573,
-0.07106810808181763,
-0.05286090821027756,
0.003437798237428069,
0.021548... | -0.034217 |
[[search-aggregations-bucket-filters-aggregation]] === Filters Aggregation Defines a multi bucket aggregation where each bucket is associated with a filter. Each bucket will collect all documents that match its associated filter. Example: [source,js] -------------------------------------------------- PUT /logs/\_doc/\_... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/filters-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.029620083048939705,
0.07453479617834091,
0.05232365056872368,
0.09449008852243423,
0.028509754687547684,
0.0025947170797735453,
-0.0429920069873333,
-0.032773457467556,
0.09673046320676804,
-0.010522308759391308,
-0.042733967304229736,
-0.038748547434806824,
0.047973811626434326,
-0.000... | 0.014809 |
{ "doc\_count": 1 }, "warnings": { "doc\_count": 2 }, "other\_messages": { "doc\_count": 1 } } } } } -------------------------------------------------- // TESTRESPONSE[s/"took": 3/"took": $body.took/] // TESTRESPONSE[s/"\_shards": \.\.\./"\_shards": $body.\_shards/] // TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/] | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/filters-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.021267153322696686,
0.08107610046863556,
0.05708228424191475,
0.07378008961677551,
0.03851281851530075,
-0.029768625274300575,
0.04903838410973549,
0.006369561422616243,
0.11656902730464935,
0.007258124183863401,
0.02433568425476551,
-0.07140140235424042,
0.08990265429019928,
0.030641438... | 0.05684 |
[[search-aggregations-bucket-histogram-aggregation]] === Histogram Aggregation A multi-bucket values source based aggregation that can be applied on numeric values extracted from the documents. It dynamically builds fixed size (a.k.a. interval) buckets over the values. For example, if the documents have a field that ho... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/histogram-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04151057451963425,
0.1093137189745903,
-0.029187023639678955,
0.003227327484637499,
-0.08217041939496994,
0.012362492270767689,
-0.03973269835114479,
0.0813744068145752,
0.06548958271741867,
-0.027859440073370934,
-0.09750071913003922,
-0.035918764770030975,
0.12101183831691742,
-0.0434... | 0.037795 |
all products (documents) have prices higher than `100`, the first bucket you'll get will be the one with `100` as its key. This is confusing, as many times, you'd also like to get those buckets between `0 - 100`. With `extended\_bounds` setting, you now can "force" the histogram aggregation to start building buckets on... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/histogram-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.008844848722219467,
0.09360137581825256,
0.020051388069987297,
-0.033675819635391235,
-0.041605960577726364,
0.028138617053627968,
-0.0014718766324222088,
0.0812598168849945,
-0.005626106169074774,
-0.008102518506348133,
-0.029172232374548912,
-0.03547446429729462,
0.09406203776597977,
-... | -0.015918 |
TEST[setup:sales] <1> Documents without a value in the `quantity` field will fall into the same bucket as documents that have the value `0`. | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/histogram-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.033121559768915176,
0.09581396728754044,
-0.02503463625907898,
0.03613025322556496,
-0.04814060032367706,
0.007311652414500713,
-0.06370263546705246,
0.02219252660870552,
0.1241859644651413,
-0.026296667754650116,
0.06551379710435867,
-0.024150647222995758,
0.04814380034804344,
0.0121264... | -0.024398 |
[[search-aggregations-bucket-filter-aggregation]] === Filter Aggregation Defines a single bucket of all the documents in the current document set context that match a specified filter. Often this will be used to narrow down the current aggregation context to a specific set of documents. Example: [source,js] -----------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/filter-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.030596420168876648,
0.10485727339982986,
0.03294888883829117,
0.10934874415397644,
0.04745069518685341,
0.052955348044633865,
-0.007600210141390562,
0.033974483609199524,
0.09051494300365448,
-0.05940889194607735,
-0.055969033390283585,
-0.04614556208252907,
-0.0025660363025963306,
-0.0... | -0.001513 |
[[search-aggregations-bucket-range-aggregation]] === Range Aggregation A multi-bucket value source based aggregation that enables the user to define a set of ranges - each representing a bucket. During the aggregation process, the values extracted from each document will be checked against each bucket range and "bucket... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/range-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04243151843547821,
0.10144789516925812,
0.011845475994050503,
0.050673674792051315,
0.014192774891853333,
0.06942799687385559,
-0.036703988909721375,
0.009423982352018356,
0.08783121407032013,
-0.07457008212804794,
-0.08043891191482544,
-0.05625630170106888,
0.047547847032547,
-0.022919... | -0.034982 |
"aggs" : { "price\_ranges" : { "range" : { "script" : { "id": "convert\_currency", <1> "params": { <2> "field": "price", "conversion\_rate": 0.835526591 } }, "ranges" : [ { "from" : 0, "to" : 100 }, { "from" : 100 } ] } } } } -------------------------------------------------- // CONSOLE // TEST[s/GET \/\_search/GET \/\... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/range-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.004870193544775248,
0.10683305561542511,
-0.07623960822820663,
0.08092417567968369,
-0.05656684562563896,
0.05788761004805565,
-0.007784719578921795,
0.07017586380243301,
0.04747573658823967,
0.001419037114828825,
-0.02529597468674183,
-0.12083999067544937,
-0.0049490612000226974,
-0.03... | 0.000388 |
[[search-aggregations-bucket-reverse-nested-aggregation]] === Reverse nested Aggregation A special single bucket aggregation that enables aggregating on parent docs from nested documents. Effectively this aggregation can break out of the nested block structure and link to other nested structures or the root document, w... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/reverse-nested-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.07750143855810165,
0.052046436816453934,
0.09141287952661514,
0.11280011385679245,
-0.032062601298093796,
-0.0028531921561807394,
-0.08161285519599915,
0.040585946291685104,
0.1086713895201683,
-0.021189464256167412,
-0.07853973656892776,
0.02068955823779106,
0.014097844250500202,
0.013... | 0.004716 |
[[search-aggregations-bucket-nested-aggregation]] === Nested Aggregation A special single bucket aggregation that enables aggregating nested documents. For example, lets say we have an index of products, and each product holds the list of resellers - each having its own price for the product. The mapping could look lik... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/nested-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.02908720076084137,
0.06066048517823219,
0.03485170379281044,
0.07055448740720749,
-0.031434331089258194,
0.052606355398893356,
-0.05750558525323868,
0.06010916456580162,
0.08324629813432693,
-0.021300194784998894,
-0.044118497520685196,
-0.013330168090760708,
0.03629845008254051,
0.0222... | -0.026997 |
[[search-aggregations-bucket-sampler-aggregation]] === Sampler Aggregation A filtering aggregation used to limit any sub aggregations' processing to a sample of the top-scoring documents. .Example use cases: \* Tightening the focus of analytics to high-relevance matches rather than the potentially very long tail of low... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/sampler-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.08892031759023666,
0.04631229117512703,
0.0035015512257814407,
0.0539989098906517,
0.0451776385307312,
0.031123187392950058,
0.016423046588897705,
0.03620040416717529,
0.0804615318775177,
-0.03680987283587456,
-0.06129738688468933,
-0.007767453324049711,
0.06458768248558044,
-0.02319878... | 0.11551 |
[[search-aggregations-bucket-iprange-aggregation]] === IP Range Aggregation Just like the dedicated <> range aggregation, there is also a dedicated range aggregation for IP typed fields: Example: [source,js] -------------------------------------------------- GET /ip\_addresses/\_search { "size": 10, "aggs" : { "ip\_ran... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/iprange-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.004195684567093849,
0.07980386167764664,
0.023645587265491486,
0.076899453997612,
-0.010352695360779762,
0.05184204876422882,
-0.02517567202448845,
-0.009722184389829636,
0.05706874653697014,
-0.059885092079639435,
-0.04953794181346893,
-0.033723920583724976,
0.01719304919242859,
-0.0137... | -0.004869 |
[[search-aggregations-bucket-daterange-aggregation]] === Date Range Aggregation A range aggregation that is dedicated for date values. The main difference between this aggregation and the normal <> aggregation is that the `from` and `to` values can be expressed in <> expressions, and it is also possible to specify a da... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/daterange-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.044056713581085205,
0.09351929277181625,
0.03493381664156914,
0.08163125813007355,
-0.028036775067448616,
0.08838595449924469,
-0.08986102044582367,
0.04250987991690636,
0.08309104293584824,
-0.059592343866825104,
-0.04072276130318642,
-0.028344497084617615,
0.006084207445383072,
-0.028... | 0.01004 |
The minimum number of digits. Shorter numbers are zero-padded to this amount. Year:: Numeric presentation for year and weekyear fields are handled specially. For example, if the count of 'y' is 2, the year will be displayed as the zero-based year of the century, which is two digits. Month:: 3 or over, use text, otherwi... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/daterange-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.02394424006342888,
0.10535964369773865,
-0.047909218817949295,
0.03788172826170921,
-0.01567917875945568,
0.00030004349537193775,
-0.05678146332502365,
-0.005393788684159517,
-0.034483715891838074,
-0.01914425566792488,
-0.020540941506624222,
-0.07152821868658066,
0.01851603388786316,
0... | 0.019296 |
[[search-aggregations-bucket-geodistance-aggregation]] === Geo Distance Aggregation A multi-bucket aggregation that works on `geo\_point` fields and conceptually works very similar to the <> aggregation. The user can define a point of origin and a set of distance range buckets. The aggregation evaluate the distance of ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/geodistance-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.003113050712272525,
0.06766730546951294,
0.032330743968486786,
0.0007730870856903493,
-0.007312437519431114,
0.05963706597685814,
-0.06905897706747055,
0.008462410420179367,
0.09840944409370422,
-0.05039215832948685,
-0.05197256803512573,
-0.015390655025839806,
0.052716437727212906,
0.0... | 0.035922 |
"ranges" : [ { "to" : 100 }, { "from" : 100, "to" : 300 }, { "from" : 300 } ] } } } } -------------------------------------------------- // CONSOLE // TEST[continued] ==== Keyed Response Setting the `keyed` flag to `true` will associate a unique string key with each bucket and return the ranges as a hash rather than an... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/geodistance-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.028077242895960808,
0.09575758129358292,
-0.01659928448498249,
0.0009853269439190626,
-0.007076147943735123,
-0.009744119830429554,
0.004700820427387953,
-0.024597156792879105,
0.06794861704111099,
-0.08966720849275589,
-0.043213170021772385,
-0.013456250540912151,
0.014571821317076683,
... | -0.01212 |
[[search-aggregations-bucket-diversified-sampler-aggregation]] === Diversified Sampler Aggregation Like the `sampler` aggregation this is a filtering aggregation used to limit any sub aggregations' processing to a sample of the top-scoring documents. The `diversified\_sampler` aggregation adds the ability to limit the ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/diversified-sampler-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.06410262733697891,
-0.0025028507225215435,
-0.00792793370783329,
0.013624160550534725,
0.06990412622690201,
0.021231498569250107,
0.043301086872816086,
0.037757571786642075,
0.0945604220032692,
-0.07210752367973328,
-0.08971183747053146,
-0.015631306916475296,
0.061693884432315826,
-0.0... | 0.11642 |
] } } } } -------------------------------------------------- // TESTRESPONSE[s/\.\.\./"took": $body.took,"timed\_out": false,"\_shards": $body.\_shards,"hits": $body.hits,/] // TESTRESPONSE[s/2.213/$body.aggregations.my\_unbiased\_sample.keywords.buckets.0.score/] // TESTRESPONSE[s/1.34/$body.aggregations.my\_unbiased\... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/diversified-sampler-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.03442647308111191,
0.0037817840930074453,
-0.010844877921044827,
0.04053468257188797,
0.030208615586161613,
-0.05480499938130379,
0.05631435289978981,
0.039046961814165115,
0.05239896476268768,
0.061880871653556824,
-0.01493036188185215,
-0.061053451150655746,
0.07279219478368759,
-0.054... | 0.019473 |
[[search-aggregations-bucket-geohashgrid-aggregation]] === GeoHash grid Aggregation A multi-bucket aggregation that works on `geo\_point` fields and groups points into buckets that represent cells in a grid. The resulting grid can be sparse and only contains cells that have matching data. Each cell is labeled using a h... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/geohashgrid-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.033073678612709045,
0.06658746302127838,
0.028118208050727844,
-0.04734400287270546,
-0.05250309780240059,
-0.07078902423381805,
0.002511988626793027,
-0.023619359359145164,
0.052434761077165604,
-0.005717781372368336,
-0.037588898092508316,
-0.04585568979382515,
0.05836684629321098,
-0.... | 0.046993 |
outside of [1,12] will be rejected. Alternatively, the precision level can be approximated from a distance measure like "1km", "10m". The precision level is calculate such that cells will not exceed the specified size (diagonal) of the required precision. When this would lead to precision levels higher than the support... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/geohashgrid-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
0.04261860251426697,
0.0659036934375763,
0.034793321043252945,
-0.06620389968156815,
-0.04035545885562897,
-0.0587288923561573,
-0.06449173390865326,
0.0287651214748621,
0.049387119710445404,
0.01261964999139309,
-0.0229585450142622,
0.019281212240457535,
0.049262844026088715,
-0.021384906... | -0.001371 |
[[search-aggregations-bucket-global-aggregation]] === Global Aggregation Defines a single bucket of all the documents within the search execution context. This context is defined by the indices and the document types you're searching on, but is \*not\* influenced by the search query itself. NOTE: Global aggregators can... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/bucket/global-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.038297995924949646,
0.046410929411649704,
0.050408557057380676,
0.09173811227083206,
0.008988015353679657,
0.05554956570267677,
-0.02982652746140957,
0.0395466610789299,
0.08405520766973495,
-0.06035682559013367,
-0.03534724563360214,
-0.026022324338555336,
0.040637124329805374,
-0.0072... | -0.008527 |
[[search-aggregations-matrix-stats-aggregation]] === Matrix Stats The `matrix\_stats` aggregation is a numeric aggregation that computes the following statistics over a set of document fields: [horizontal] `count`:: Number of per field samples included in the calculation. `mean`:: The average value for each field. `var... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/aggregations/matrix/stats-aggregation.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.04615535959601402,
-0.022688785567879677,
-0.08872746676206589,
0.049098506569862366,
-0.06942736357450485,
-0.020687850192189217,
-0.020394347608089447,
0.047375693917274475,
0.10478055477142334,
-0.01649661920964718,
0.015821406617760658,
0.03134889900684357,
0.0479545071721077,
-0.00... | 0.190139 |
[[breaking-changes-6.0]] == Breaking changes in 6.0 This section discusses the changes that you need to be aware of when migrating your application to Elasticsearch 6.0. [float] === Indices created before 6.0 Elasticsearch 6.0 can read indices created in version 5.0 or above. An Elasticsearch 6.0 node will not start in... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0.asciidoc | 6.2 | elasticsearch-6-2 | [
0.03765109181404114,
-0.031856853514909744,
0.06620566546916962,
0.01064392738044262,
0.04244191199541092,
0.015741217881441116,
-0.07216235995292664,
-0.039374493062496185,
-0.05337642878293991,
0.05858885869383812,
-0.06228791922330856,
-0.02332940138876438,
-0.06909263879060745,
-0.0652... | 0.041603 |
[[breaking-changes-6.1]] == Breaking changes in 6.1 [[breaking\_61\_packaging]] [float] === Bootstrap checks now apply to link-local addresses Previously when Elasticsearch was bound to localhost, Elasticsearch would bind to any address on the loopback device. This included link-local addresses on the loopback device s... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_1.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.005207453388720751,
0.059085410088300705,
0.06236663833260536,
0.017525380477309227,
0.14679384231567383,
-0.02445187419652939,
-0.06615883857011795,
-0.06419426947832108,
-0.024513278156518936,
-0.011902141384780407,
0.020742982625961304,
0.07415062934160233,
-0.005532962270081043,
-0.... | -0.021092 |
[[breaking-changes]] = Breaking changes [partintro] -- This section discusses the changes that you need to be aware of when migrating your application from one version of Elasticsearch to another. As a general rule: \* Migration between minor versions -- e.g. `6.x` to `6.y` -- can be performed by <>. \* Migration betwe... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/index.asciidoc | 6.2 | elasticsearch-6-2 | [
0.05154251307249069,
-0.009791025891900063,
0.0878840982913971,
-0.027624202892184258,
0.060703083872795105,
0.01707725040614605,
-0.1060313954949379,
-0.00499426294118166,
-0.044531334191560745,
0.005814660340547562,
-0.022431286051869392,
-0.03882749006152153,
-0.0673743262887001,
-0.051... | 0.032393 |
[[breaking-changes-6.2]] == Breaking changes in 6.2 [[breaking\_62\_packaging]] [float] === All permission bootstrap check Elasticsearch installs a security manager during bootstrap to mitigate the scope of exploits in the JDK, in third-party dependencies, and in Elasticsearch itself as well as to sandbox untrusted plu... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_2.asciidoc | 6.2 | elasticsearch-6-2 | [
0.005078737623989582,
0.0954669937491417,
-0.02573133446276188,
-0.04653702303767204,
0.08033474534749985,
-0.05153725668787956,
-0.06758083403110504,
-0.004333868622779846,
-0.03453602269291878,
0.0698900818824768,
-0.010298153385519981,
-0.019302310422062874,
0.00926248636096716,
0.02130... | 0.045796 |
[[breaking\_60\_scripting\_changes]] === Scripting changes ==== Groovy, JavaScript, and Python languages removed The Groovy, JavaScript, and Python scripting languages were deprecated in elasticsearch 5.0 and have now been removed. Use painless instead. ==== Native scripts removed Native scripts have been removed. Inst... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/scripting.asciidoc | 6.2 | elasticsearch-6-2 | [
0.015018070116639137,
0.08245468139648438,
0.06047334894537926,
0.07509023696184158,
-0.008730980567634106,
0.00906513724476099,
-0.08114122599363327,
0.02928007021546364,
0.01937350071966648,
0.012711137533187866,
-0.06509575992822647,
-0.0036422014236450195,
-0.05629599839448929,
-0.0492... | 0.0494 |
[[breaking\_60\_mappings\_changes]] === Mapping changes ==== Coercion of boolean fields Previously, Elasticsearch recognized the strings `true`, `false`, `on`, `off`, `yes`, `no`, `0`, `1` as booleans. Elasticsearch 6.0 recognizes only the strings `true` and `false` as booleans and will throw an error otherwise. For ba... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/mappings.asciidoc | 6.2 | elasticsearch-6-2 | [
0.055556926876306534,
0.03247024491429329,
0.05908413976430893,
0.008311241865158081,
0.0006579222972504795,
0.046598564833402634,
-0.09424833953380585,
-0.06199502572417259,
-0.04405008628964424,
0.044752057641744614,
-0.007949075661599636,
0.008078564889729023,
-0.04348194599151611,
0.00... | 0.03205 |
[[breaking\_60\_analysis\_changes]] === Analysis changes ==== Synonym Token Filter In 6.0, Synonym Token Filter tokenizes synonyms with whatever tokenizer and token filters appear before it in the chain. The `tokenizer` and `ignore\_case` parameters are deprecated and will be ignored when used in new indices. These par... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/analysis.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.0012162222992628813,
0.0463886484503746,
0.010165617801249027,
0.025799309834837914,
0.02990732528269291,
0.0055096931755542755,
0.004718291573226452,
0.004856409505009651,
0.037839051336050034,
0.0036693434230983257,
-0.01558021828532219,
0.016161466017365456,
0.018205588683485985,
0.0... | 0.128733 |
[[breaking\_60\_settings\_changes]] === Settings changes ==== Remove support for elasticsearch.json and elasticsearch.yaml configuration file The configuration file found in the Elasticsearch config directory could previously have a `.yml`, `.yaml` or `.json` extension. Only `elasticsearch.yml` is now supported. ==== D... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/settings.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.001096876454539597,
0.04892909526824951,
0.024428218603134155,
0.00024363752163480967,
0.019160818308591843,
0.013372167944908142,
-0.04071496054530144,
-0.051943182945251465,
0.01651918888092041,
0.0181269571185112,
0.008710806258022785,
0.05103394016623497,
0.02933434024453163,
-0.069... | 0.015672 |
[[breaking\_60\_search\_changes]] === Search and Query DSL changes ==== Changes to queries \* The `collect\_payloads` parameter of the `span\_near` query has been removed. Payloads will be loaded when needed. \* Queries on boolean fields now strictly parse boolean-like values. This means only the strings `"true"` and `... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/search.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.022988349199295044,
0.020846586674451828,
0.042607273906469345,
0.05503518134355545,
-0.03474109619855881,
-0.034438278526067734,
0.012062467634677887,
-0.04728337377309799,
-0.03180777654051781,
0.009719060733914375,
0.02813354693353176,
0.006774386391043663,
0.08200085908174515,
-0.05... | 0.094178 |
from the `match` query but is supported for `match\_phrase` and `match\_phrase\_prefix`. \* The deprecated `phrase\_slop` parameter (a synonym for the `slop` parameter) of the `match\_phrase` query has been removed. \* The deprecated `query` parameter (a synonym for the `filter` parameter) of the `constant\_score` quer... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/search.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.048939600586891174,
0.00024799653328955173,
0.03126094490289688,
-0.0038416036404669285,
-0.023489004001021385,
0.03281484916806221,
0.020443132147192955,
0.02729438617825508,
-0.01655425690114498,
-0.007054740563035011,
0.04724791646003723,
0.006950777024030685,
0.04592256247997284,
-0... | 0.084181 |
be overridden by using the `index.max\_script\_fields` index setting. ==== Inner hits The source inside a hit of inner hits keeps its full path with respect to the entire source. In prior versions the source field names were relative to the inner hit. ==== Scroll The `from` parameter can no longer be used in the search... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/search.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.033305130898952484,
0.04904179275035858,
0.0038746497593820095,
0.08072362840175629,
0.0039898911491036415,
-0.042930178344249725,
0.028755752369761467,
0.025444941595196724,
-0.0038420245982706547,
0.02117372862994671,
-0.08085858821868896,
0.05151236429810524,
0.05816945806145668,
-0.... | 0.040111 |
[[breaking\_60\_java\_changes]] === Java API changes [[\_literal\_setsource\_literal\_methods\_require\_xcontenttype]] ==== `setSource` methods require XContentType Previously the `setSource` methods and other methods that accepted byte/string representations of an object source did not require the XContentType to be s... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/java.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.02923884056508541,
0.021066898480057716,
0.02086421474814415,
0.020625295117497444,
0.018684590235352516,
0.014606061391532421,
0.033771149814128876,
-0.034187283366918564,
0.05034454166889191,
-0.0016042091883718967,
-0.05315246060490608,
-0.017282985150814056,
0.034410666674375534,
-0... | 0.075562 |
[[breaking\_60\_ingest\_changes]] === Ingest changes ==== Timestamp meta-data field type has changed The type of the "timestamp" meta-data field has changed from `java.lang.String` to `java.util.Date`. ==== The format of the string-formatted ingest.timestamp field has changed Previously, since Elasticsearch 5.4.0, you ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/ingest.asciidoc | 6.2 | elasticsearch-6-2 | [
0.06091700494289398,
0.09053979068994522,
0.11549746245145798,
0.010423836298286915,
-0.018364598974585533,
0.016698237508535385,
-0.046112168580293655,
0.034156396985054016,
-0.027776440605521202,
0.03558148816227913,
-0.06970416754484177,
-0.06676080822944641,
-0.04433884844183922,
0.034... | 0.002468 |
[[breaking\_60\_cluster\_changes]] === Cluster changes ==== Cluster name no longer allowed in path.data Previously the cluster name could be used in the `path.data` setting with a warning. This is now no longer allowed. For instance, in the previous version this was valid: [source,sh] ----------------------------------... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/cluster.asciidoc | 6.2 | elasticsearch-6-2 | [
0.04800642654299736,
0.01679696887731552,
0.0005201459280215204,
0.03991436958312988,
0.04268879443407059,
-0.009578856639564037,
-0.02411206252872944,
-0.00811287946999073,
-0.03117486648261547,
0.06242278218269348,
0.061460353434085846,
-0.09025683254003525,
0.010289751924574375,
-0.0509... | 0.056615 |
[[breaking\_60\_docs\_changes]] === Document API changes [[\_version\_type\_literal\_force\_literal\_removed]] ==== version type `force` removed Document modification operations may no longer specify the `version\_type` of `force` to override any previous version checks. [[\_link\_linkend\_upserts\_upserts\_link\_no\_l... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/docs.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.1060541570186615,
0.055133286863565445,
0.07576248794794083,
0.038551490753889084,
0.015292420983314514,
0.0013973747845739126,
-0.05889574810862541,
-0.05939798057079315,
-0.022873176261782646,
0.06304068118333817,
0.02153470367193222,
0.037126846611499786,
0.018506640568375587,
-0.028... | 0.093241 |
[[breaking\_60\_geo\_changes]] === Geo changes [[\_deprecated\_literal\_shapebuilders\_literal\_helper\_class]] ==== Deprecated `ShapeBuilders` helper class The `ShapeBuilders` class containing static methods to create shape specific builders (e.g., `ShapeBuilders.newPoint`) has been deprecated. One must now use the bu... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/geo.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.01937463879585266,
-0.014711732044816017,
0.05359677970409393,
0.0018675049068406224,
-0.10315979272127151,
0.012822134420275688,
-0.07838878035545349,
0.03231438249349594,
-0.14892764389514923,
-0.016877776011824608,
-0.008336625061929226,
-0.09841938316822052,
0.002637015888467431,
-0... | -0.002921 |
[[breaking\_60\_rest\_changes]] === REST changes ==== Unquoted JSON In previous versions of Elasticsearch, JSON documents were allowed to contain unquoted field names. This feature was removed in the 5.x series, but a backwards-compatibility layer was added via the system property `elasticsearch.json.allow\_unquoted\_f... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/rest.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.0774950236082077,
0.01701677031815052,
0.09677796065807343,
0.017947247251868248,
-0.006512426305562258,
-0.011423192918300629,
-0.09002460539340973,
-0.08983390033245087,
0.08514075726270676,
0.033100977540016174,
-0.016838936135172844,
0.022895706817507744,
0.010104208253324032,
-0.00... | 0.050452 |
`Allow` header is added to the 405 responses containing the allowed verbs. For example: [source,text] ------------------------------------------- $ curl -v -XPOST 'localhost:9200/my\_index/\_settings' \* Trying 127.0.0.1... \* TCP\_NODELAY set \* Connected to localhost (127.0.0.1) port 9200 (#0) > POST /my\_index/\_set... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/rest.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.001606046804226935,
0.07546254992485046,
-0.012270273640751839,
-0.06545104831457138,
-0.04565295949578285,
-0.03951864689588547,
-0.09303714334964752,
-0.048953160643577576,
-0.06166831776499748,
-0.022069279104471207,
0.04338816553354263,
0.012820839881896973,
0.024539638310670853,
0.... | -0.036927 |
[[breaking\_60\_plugins\_changes]] === Plugins changes ==== Mapper attachments plugin \* The mapper attachments plugin has been deprecated in elasticsearch 5.0 and is now removed. You can use {plugins}/ingest-attachment.html[ingest attachment plugin] instead. ==== S3 Repository plugin \* The bucket an s3 repository is ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/plugins.asciidoc | 6.2 | elasticsearch-6-2 | [
0.0006005820468999445,
-0.031374551355838776,
-0.03126918524503708,
-0.009374917484819889,
0.023122210055589676,
0.03863627091050148,
-0.0718018189072609,
-0.05257062986493111,
0.06274885684251785,
0.10882660746574402,
0.004966930951923132,
-0.02814421057701111,
0.02062339521944523,
0.0442... | -0.003519 |
[[breaking\_60\_packaging\_changes]] === Packaging changes ==== Configuring custom user and group for package is no longer allowed Previously someone could configure the `$ES\_USER` and `$ES\_GROUP` variables to change which user and group Elasticsearch was run as. This is no longer possible, the DEB and RPM packages n... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/packaging.asciidoc | 6.2 | elasticsearch-6-2 | [
0.013329853303730488,
0.02872087061405182,
0.008956699632108212,
-0.0227273590862751,
0.0165939349681139,
0.009560918435454369,
-0.014482621103525162,
0.017998075112700462,
-0.06173880398273468,
0.01728515326976776,
0.020396625623106956,
-0.05066167563199997,
-0.0017128491308540106,
-0.004... | 0.046318 |
environment variable is already used in the packaging to support relocating the configuration files so this change merely aligns the other configuration files with the location of the `jvm.options` file. [[\_literal\_es\_include\_literal\_is\_no\_longer\_supported]] ==== `ES\_INCLUDE` is no longer supported The environ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/packaging.asciidoc | 6.2 | elasticsearch-6-2 | [
0.03825174272060394,
-0.008234553039073944,
0.06327806413173676,
-0.0016248644096776843,
0.08069662749767303,
0.017728546634316444,
-0.04650180786848068,
0.00913013145327568,
-0.02931824140250683,
0.0005031368345953524,
0.040082238614559174,
0.027915332466363907,
0.00953618809580803,
0.036... | -0.002441 |
[[breaking\_60\_stats\_changes]] === Stats and info changes [[\_removal\_of\_literal\_throttle\_time\_literal\_in\_the\_literal\_store\_literal\_stats]] ==== Removal of `throttle\_time` in the `store` stats Given that store throttling has been removed, the `store` stats do not report `throttle\_time` anymore. ==== FS s... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/stats.asciidoc | 6.2 | elasticsearch-6-2 | [
0.009853633120656013,
0.0902307778596878,
-0.00911850668489933,
0.05521398037672043,
0.0232847910374403,
-0.043269433081150055,
-0.08760333061218262,
-0.001286022481508553,
0.025816310197114944,
0.07751844078302383,
0.003972128964960575,
0.05295571684837341,
0.026798129081726074,
-0.055239... | 0.064564 |
[[breaking\_60\_indices\_changes]] === Indices changes [[\_index\_templates\_use\_literal\_index\_patterns\_literal\_instead\_of\_literal\_template\_literal]] ==== Index templates use `index\_patterns` instead of `template` Previously templates expressed the indices that they should match using a glob style pattern in ... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/indices.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.05363161116838455,
0.10162196308374405,
0.06458727270364761,
0.05352478846907616,
-0.05922955274581909,
0.04122689366340637,
0.037703756242990494,
-0.03778960555791855,
0.006966670975089073,
-0.06961045414209366,
-0.07953166961669922,
0.004747538827359676,
-0.051504094153642654,
-0.0606... | 0.044622 |
[[breaking\_60\_aggregations\_changes]] === Aggregations changes [[\_deprecated\_literal\_pattern\_literal\_element\_of\_include\_exclude\_for\_terms\_aggregations\_has\_been\_removed]] ==== Deprecated `pattern` element of include/exclude for terms aggregations has been removed The `include` and `exclude` options of `t... | https://github.com/elastic/elasticsearch/blob/6.2//docs/reference/migration/migrate_6_0/aggregations.asciidoc | 6.2 | elasticsearch-6-2 | [
-0.06878694146871567,
0.11546023190021515,
0.074324831366539,
0.07407272607088089,
0.02465420961380005,
0.022810153663158417,
0.004387352149933577,
-0.026495281606912613,
0.04712553694844246,
-0.026929697021842003,
0.01883065514266491,
-0.008531065657734871,
0.003837721422314644,
-0.057358... | 0.02096 |
= Extending with Shared Libraries As Pipeline is adopted for more and more projects in an organization, common patterns are likely to emerge. Oftentimes it is useful to share parts of Pipelines between various projects to reduce redundancies and keep code "DRY" footnote:dry[https://en.wikipedia.org/wiki/Don\'t\_repeat\... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/shared-libraries.adoc | main | jenkins | [
-0.07734901458024979,
-0.0827336236834526,
-0.03250660002231598,
-0.0267778467386961,
0.06332879513502121,
-0.032967839390039444,
-0.027285994961857796,
0.014574113301932812,
0.016522599384188652,
-0.08813299238681793,
-0.02028142288327217,
0.044630542397499084,
-0.03410881757736206,
0.020... | 0.096014 |
source files in these directories get the same “CPS transformation” as in Scripted Pipeline. A `resources` directory allows the `libraryResource` step to be used from an external library to load associated non-Groovy files. Currently this feature is not supported for internal libraries. Other directories under the root... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/shared-libraries.adoc | main | jenkins | [
-0.08769119530916214,
-0.005638237576931715,
-0.023003248497843742,
-0.047927357256412506,
0.08055150508880615,
-0.06249618902802467,
-0.0024026238825172186,
0.022111032158136368,
0.029132621362805367,
-0.06661272794008255,
-0.017094740644097328,
-0.03895069286227226,
0.021624568849802017,
... | -0.000373 |
type declarations in the script, for example: [source,groovy] ---- @Library('somelib') import com.mycorp.pipeline.somelib.Helper int useSomeLib(Helper helper) { helper.prepare() return helper.count() } echo useSomeLib(new Helper('some text')) ---- Global Variables however, are resolved at runtime. This video reviews us... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/shared-libraries.adoc | main | jenkins | [
0.0017299782484769821,
-0.045332394540309906,
-0.06802750378847122,
-0.011605950072407722,
0.03758031502366066,
0.011905252002179623,
0.06190124526619911,
0.025005947798490524,
-0.020180922001600266,
-0.13571983575820923,
0.005838146433234215,
-0.01514318399131298,
-0.030911799520254135,
0... | -0.032507 |
features required by Shared Libraries, may still be used via the \*\*Legacy SCM\*\* option. In this case, include `${library.yourlibrarynamehere.version}` wherever a branch/tag/ref may be configured for that particular SCM plugin. This ensures that during checkout of the library's source code, the SCM plugin will expan... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/shared-libraries.adoc | main | jenkins | [
0.0010905530070886016,
-0.05145295709371567,
0.03773058205842972,
-0.009623770602047443,
0.09027925878763199,
0.03756145015358925,
-0.07107394188642502,
-0.027815144509077072,
-0.04628957435488701,
-0.1102481484413147,
-0.05452859774231911,
0.01551374327391386,
0.012334773316979408,
0.0262... | -0.038546 |
\_ log.info 'Starting' log.warning 'Nothing to do!' ---- Declarative Pipeline does not allow method calls on objects outside "script" blocks. (link:https://issues.jenkins.io/browse/JENKINS-42360[JENKINS-42360]). The method calls above would need to be put inside a `script` directive: .Jenkinsfile [source,groovy] ---- @... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/shared-libraries.adoc | main | jenkins | [
0.002870406024158001,
0.04657427966594696,
-0.006849283818155527,
-0.016621656715869904,
-0.0008089838665910065,
-0.08232877403497696,
-0.009569009765982628,
0.032772477716207504,
-0.011267240159213543,
-0.029668129980564117,
-0.05158580094575882,
-0.056622039526700974,
-0.020293720066547394... | 0.011102 |
// buildPlugin name: 'git' // Declarative not yet implemented // ---- There is also a “builder pattern” trick using Groovy’s `Closure.DELEGATE\_FIRST`, which permits `Jenkinsfile` to look slightly more like a configuration file than a program, but this is more complex and error-prone and is not recommended. [#using-thi... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/shared-libraries.adoc | main | jenkins | [
-0.08357113599777222,
-0.021187087520956993,
-0.04326720908284187,
-0.034895554184913635,
-0.03972933068871498,
-0.05418063700199127,
-0.008385125547647476,
0.02175106666982174,
0.004187588579952717,
-0.050824280828237534,
-0.03243015706539154,
-0.049203060567379,
0.03397582843899727,
0.00... | -0.051858 |
fail as a result. [#testing-library-pull-request-changes] === Testing library pull request changes By adding `@Library('my-shared-library@pull//head') \_` at the top of a library consumer Jenkinsfile, you can test your pipeline library pull request changes \_\_in situ\_\_ if your pipeline library is hosted on GitHub an... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/shared-libraries.adoc | main | jenkins | [
-0.08343653380870819,
-0.09119823575019836,
0.0066688950173556805,
0.002017081482335925,
0.04889566823840141,
-0.05525185167789459,
-0.08625033497810364,
-0.029352828860282898,
-0.0027969246730208397,
-0.017844321206212044,
-0.011566284112632275,
-0.05111154913902283,
-0.0056365299969911575,... | 0.006765 |
= Branches and Pull Requests In the xref:./jenkinsfile.adoc[previous section] a `Jenkinsfile` which could be checked into source control was implemented. This section covers the concept of \*Multibranch\* Pipelines which build on the `Jenkinsfile` foundation to provide more dynamic and automatic functionality in Jenkin... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/multibranch.adoc | main | jenkins | [
-0.02291139028966427,
-0.11629237234592438,
-0.04752242937684059,
-0.027272839099168777,
-0.01902681775391102,
-0.07375306636095047,
-0.0508178249001503,
-0.0024569835513830185,
0.023785829544067383,
-0.019741535186767578,
-0.07965900003910065,
-0.03485874831676483,
-0.007299648132175207,
... | 0.04403 |
= Pipeline Development Tools Jenkins Pipeline includes xref:./getting-started.adoc#built-in-documentation[built-in documentation] and the xref:./getting-started.adoc#snippet-generator[Snippet Generator] which are key resources when developing Pipelines. They provide detailed help and information that is customized to t... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/development.adoc | main | jenkins | [
-0.06251154839992523,
-0.06088291481137276,
-0.04811985790729523,
-0.019564470276236534,
0.023492464795708656,
-0.08365081250667572,
-0.022537197917699814,
0.010418303310871124,
-0.026252584531903267,
-0.03967325761914253,
-0.04059186577796936,
-0.07309283316135406,
-0.03012894093990326,
-... | 0.047302 |
== Running a Pipeline // TODO: WEBSITE-495 - flesh out placeholder sections. === Multibranch See xref:./multibranch.adoc[the Multibranch documentation] for more information. === Parameters See xref:./jenkinsfile.adoc#handling-parameters[the Jenkinsfile documentation] for more information == Restarting or Rerunning a Pi... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/running-pipelines.adoc | main | jenkins | [
0.01289980486035347,
-0.07183638960123062,
-0.0018146595684811473,
-0.013866987079381943,
-0.04870957136154175,
-0.045953329652547836,
-0.0595865361392498,
-0.025650691241025925,
-0.042648766189813614,
-0.07215864956378937,
-0.049181073904037476,
-0.012801526114344597,
-0.057952068746089935,... | 0.009742 |
// or preserveStashes(buildCount: 5) // <2> } ---- <1> The default number of runs to preserve is 1, just the most recent completed build. <2> If a number for `buildCount` outside of the range of 1 to 50 is specified, the Pipeline will fail with a validation error. When a Pipeline completes, it will check to see if any ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/running-pipelines.adoc | main | jenkins | [
-0.03819803521037102,
0.0023467233404517174,
0.046403463929891586,
0.011030766181647778,
-0.04162757843732834,
-0.05601798743009567,
-0.13142400979995728,
-0.05665148049592972,
-0.011784135363996029,
-0.036896850913763046,
-0.09729453921318054,
-0.003548197913914919,
-0.012370707467198372,
... | 0.001298 |
:page-aliases: user-docs:pipeline:overview.adoc = Getting started with Pipeline As mentioned xref:index.adoc[previously], Jenkins Pipeline is a suite of plugins that supports implementing and integrating continuous delivery pipelines into Jenkins. Pipeline provides an extensible set of tools for modeling simple-to-comp... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/getting-started.adoc | main | jenkins | [
-0.10434038192033768,
-0.0640062764286995,
0.008383022621273994,
-0.01194757129997015,
-0.042400941252708435,
-0.06533748656511307,
-0.010757301934063435,
0.015016715042293072,
0.00965450331568718,
-0.04199722036719322,
-0.07800088822841644,
-0.033699795603752136,
-0.011934025213122368,
0.... | 0.072707 |
It is recommended to avoid using spaces in item names, since doing so may uncover bugs in scripts that do not properly handle spaces in directory paths. . Scroll down and click \*Pipeline\*, then click \*OK\* at the end of the page to open the Pipeline configuration page (whose \*General\* tab is selected). + [.boxshad... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/getting-started.adoc | main | jenkins | [
0.007966045290231705,
-0.02807311899960041,
0.04674050584435463,
0.0619763508439064,
-0.022916968911886215,
-0.016466232016682625,
-0.018965596333146095,
0.005864418111741543,
0.007868749089539051,
0.03903525322675705,
-0.011389574967324734,
-0.036285340785980225,
0.03931356966495514,
-0.0... | -0.051593 |
UI's] \*Script\* text area of the Pipeline configuration page. To make this easier, your Pipeline's `Jenkinsfile` can be written in a text editor or integrated development environment (IDE) and committed to source control footnote:scm[] (optionally with the application code that Jenkins will build). Jenkins can then ch... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/getting-started.adoc | main | jenkins | [
-0.006677505560219288,
-0.040289733558893204,
-0.03202880173921585,
0.004358226433396339,
-0.004216129891574383,
-0.01012501958757639,
-0.03624291345477104,
0.07944311946630478,
-0.032534338533878326,
-0.024867333471775055,
-0.0746263638138771,
-0.07801630347967148,
0.02501416578888893,
-0... | 0.006143 |
reference to "Generate Pipeline Script" button which needs to be renamed in a future release of Pipeline: https://issues.jenkins.io/browse/JENKINS-40550 //// [.boxshadow] image:user-docs:pipeline:snippet-generator.png[alt="Snippet Generator",width=100%] To access additional information and/or documentation about the st... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/getting-started.adoc | main | jenkins | [
-0.03564949333667755,
-0.006792491767555475,
0.049237146973609924,
0.04663781076669693,
0.0038405435625463724,
0.011812728829681873,
-0.04868004471063614,
-0.030457358807325363,
-0.00020094927458558232,
-0.0349898636341095,
-0.08488480001688004,
-0.04950100928544998,
0.01852058619260788,
-... | -0.007835 |
= Pipeline Best Practices This guide provides a small selection of best practices for pipelines and points out the most common mistakes. The goal is to point pipeline authors and maintainers towards patterns that result in better Pipeline execution and away from pitfalls they might otherwise not be aware of. This guide... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/pipeline-best-practices.adoc | main | jenkins | [
-0.059667330235242844,
-0.004203797318041325,
-0.04803379997611046,
-0.04737969860434532,
-0.06648693233728409,
-0.10964179039001465,
-0.04361449554562569,
0.06053794175386429,
-0.04860725253820419,
-0.019530244171619415,
-0.05776532366871834,
-0.019543569535017014,
-0.05102110281586647,
-... | -0.020291 |
to perform the HTTP request from the agent, for example using a tool like `curl` or `wget`, as appropriate. If the result must be later in the Pipeline, try to filter the result on the agent side as much as possible so that only the minimum required information must be transmitted back to the Jenkins controller. === Re... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/pipeline-best-practices.adoc | main | jenkins | [
-0.040111854672431946,
0.04253889620304108,
-0.034922558814287186,
0.007410036865621805,
-0.05621848255395889,
-0.08279301971197128,
-0.12184794992208481,
-0.04254457727074623,
0.06397150456905365,
0.01760534942150116,
-0.060631707310676575,
-0.02827398106455803,
0.01701807603240013,
-0.06... | 0.021219 |
the same. Lastly, because of the ubiquitous use of these steps throughout Pipelines, if something is coded incorrectly/inefficiently the results can be catastrophic to Jenkins. === Avoiding large global variable declaration files Having large variable declaration files can require large amounts of memory for little to ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/pipeline-best-practices.adoc | main | jenkins | [
-0.022980645298957825,
0.02914939634501934,
0.043976686894893646,
0.016959816217422485,
0.003903695149347186,
-0.08424509316682816,
-0.07443556934595108,
-0.008483008481562138,
0.08631150424480438,
0.010662179440259933,
-0.03204827010631561,
0.005030839703977108,
-0.022554239258170128,
-0.... | 0.004116 |
of calculating their value and storing that value in a variable. [#using-noncps] ==== Using `@NonCPS` If necessary, you can use the `@NonCPS` annotation to disable the CPS transformation for a specific method whose body would not execute correctly if it were CPS-transformed. Just be aware that this also means the Groov... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/pipeline-best-practices.adoc | main | jenkins | [
-0.04538130387663841,
0.05301289260387421,
-0.0893602967262268,
-0.016093537211418152,
-0.05098646879196167,
-0.047190431505441666,
-0.011968410573899746,
0.03775379806756973,
0.0001305356272496283,
-0.037167392671108246,
0.019022569060325623,
-0.06558141857385635,
-0.025824815034866333,
-... | -0.032762 |
= Using Docker with Pipeline Many organizations use link:https://www.docker.com[Docker] to unify their build and test environments across machines, and to provide an efficient mechanism for deploying applications. Starting with Pipeline versions 2.5 and higher, Pipeline has built-in support for interacting with Docker ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/docker.adoc | main | jenkins | [
-0.0247249323874712,
-0.002425986574962735,
-0.014316062442958355,
-0.028185537084937096,
-0.006494331173598766,
-0.09245770424604416,
-0.029239945113658905,
0.028385687619447708,
-0.013747172430157661,
-0.037965450435876846,
-0.08057886362075806,
-0.07382873445749283,
0.010341213084757328,
... | 0.029371 |
`~/.m2` between Pipeline runs utilizing the link:https://hub.docker.com/\_/maven/[`maven` container], avoiding the need to re-download dependencies for subsequent Pipeline runs. [pipeline] ---- // Declarative // pipeline { agent { docker { image 'maven:3.9.9-eclipse-temurin-21' args '-v $HOME/.m2:/root/.m2' } } stages ... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/docker.adoc | main | jenkins | [
-0.019026009365916252,
0.021658560261130333,
-0.000743976270314306,
-0.05855398625135422,
0.05297871679067612,
-0.08055949956178665,
-0.06467676907777786,
-0.0229168888181448,
0.044454820454120636,
-0.051780425012111664,
0.00048819807125255466,
-0.09159690141677856,
-0.0017303647473454475,
... | 0.005498 |
and should include: \* `/usr/local/bin` \* `/usr/bin` \* `/bin` \* `/usr/sbin` \* `/sbin` \* `/Applications/Docker.app/Contents/Resources/bin/` \* `/Users/XXX/Library/Group\ Containers/group.com.docker/Applications/Docker.app/Contents/Resources/bin` (where `XXX` is replaced by your user name) Now, restart jenkins using... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/docker.adoc | main | jenkins | [
-0.017884718254208565,
0.056147925555706024,
0.021417487412691116,
0.012534144334495068,
-0.005100272595882416,
-0.060528893023729324,
-0.0388936847448349,
-0.06058703362941742,
-0.022624686360359192,
-0.010861537419259548,
-0.06997920572757721,
-0.03984946757555008,
0.009721201844513416,
... | 0.000401 |
the current directory by default. This can be overridden by providing a directory path containing a `Dockerfile` as the second argument of the `build()` method, for example: [source,groovy] ---- node { checkout scm def testImage = docker.build("test-image", "./dockerfiles/test") // <1> testImage.inside { sh 'make test'... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/docker.adoc | main | jenkins | [
-0.011111867614090443,
0.02357400394976139,
-0.05733520910143852,
0.027189020067453384,
0.09254299104213715,
-0.03799360617995262,
0.032647937536239624,
0.03108711913228035,
-0.037708550691604614,
-0.0050377026200294495,
-0.008609235286712646,
-0.040599334985017776,
0.0442325659096241,
0.0... | -0.059477 |
= Using a Jenkinsfile This section builds on the information covered in xref:pipeline:getting-started.adoc[Getting started with Pipeline] and introduces more useful steps, common patterns, and demonstrates some non-trivial `Jenkinsfile` examples. Creating a `Jenkinsfile`, which is checked into source control footnote:s... | https://github.com/jenkins-infra/docs.jenkins.io/blob/main//docs/user-docs/modules/pipeline/pages/jenkinsfile.adoc | main | jenkins | [
-0.07231995463371277,
-0.05859522521495819,
-0.07170524448156357,
0.015794949606060982,
0.02502988837659359,
-0.10042790323495865,
0.00236507598310709,
0.02175714075565338,
-0.03348919749259949,
0.0029051778838038445,
-0.01355237141251564,
-0.04051739722490311,
-0.016443708911538124,
-0.05... | 0.124532 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.