| f076a79 | Alpar Torok | 02 April 2019, 15:00:22 UTC | Revert bad merge | 02 April 2019, 15:00:22 UTC |
| 0e92b98 | Jason Tedor | 02 April 2019, 12:53:45 UTC | Add migration note for Ubuntu 14.04 This commit adds a migration note to the docs for Ubuntu 14.04 seeing as it will not be supported after April 30, 2019 by upstream. | 02 April 2019, 12:54:34 UTC |
| 952ad85 | David Turner | 02 April 2019, 12:18:17 UTC | Use TAR instead of DOCKER build type before 6.7.0 (#40723) In 6.7.0 (#39378) we added a build type of DOCKER for the docker images, but unfortunately earlier versions do not understand this and will reject any transport messages that mention this build type. This commit fixes this by reporting TAR instead of DOCKER when talking to older nodes. Relates (but does not fix) #40511 Relates #39378 | 02 April 2019, 12:35:54 UTC |
| 10f0ecf | Jay Modi | 02 April 2019, 12:35:08 UTC | Remove with(out)-system-key tests (#40547) (#40604) This change removes the variants of the rolling upgrade and full cluster restart tests that use or do not use a system key. These tests were added during 5.x when the system key was still used for security and now the system key is only used as the watcher encryption key so duplicating rolling upgrade and full cluster restarts is not needed. The change here removes the subprojects for testing these scenarios and defaults to always run with the watcher sensitive values encrypted for these tests. | 02 April 2019, 12:35:08 UTC |
| ba9abc5 | Adrien Grand | 02 April 2019, 09:18:53 UTC | Update indexing speed recommendations around the refresh interval. (#40690) We now need to update recommendations now that we have introduced the concept of "search idle" shards. | 02 April 2019, 09:19:37 UTC |
| 37758bb | Alexander Reelsen | 02 April 2019, 08:26:54 UTC | Allow single digit milliseconds in strict date parsing (#40676) In order to remain compatible with the existing joda based implementation the parsing of milliseconds should support parsing single digits instead of relying on three, even with strict formats. This adds a few tests to duel against the existing joda based implementation in order to ensure the parsing behaviour is the same. Closes #40403 | 02 April 2019, 08:56:37 UTC |
| 673d381 | Christoph Büscher | 01 April 2019, 23:43:02 UTC | Correct indention in synonym docs (#40711) The stopword filter should be on the same level as the synonym filter in the example request. Correcting this for better readability. | 01 April 2019, 23:44:53 UTC |
| 8951fb4 | lcawl | 01 April 2019, 19:01:13 UTC | [DOCS] Adds placeholder for 7.0.0-rc2 release notes | 01 April 2019, 19:01:13 UTC |
| a966ffe | Benjamin Trent | 01 April 2019, 18:24:59 UTC | [ML] Addressing bug streaming DatafeedConfig aggs from (<= 6.5.4) -> 6.7.0 (#40656) * [ML] Addressing bug streaming DatafeedConfig aggs from (<= 6.5.4) -> 6.7.0 (#40610) * Addressing stream failure and adding tests to catch such in the future * Add aggs to full cluster restart tests * Test BWC for datafeeds with and without aggs The wire serialisation is different for null/non-null aggs, so it's worth testing both cases. * fixing bwc test, removal of _xpack url path * Fixing BWC test for datafeed | 01 April 2019, 18:24:59 UTC |
| 9d012ca | lcawl | 01 April 2019, 17:13:27 UTC | [DOCS] Fixes capitalization in release highlights | 01 April 2019, 17:13:27 UTC |
| 2e55abc | lcawl | 01 April 2019, 17:06:56 UTC | [DOCS] Fixes links in release highlights for re-use | 01 April 2019, 17:08:04 UTC |
| a30d5ab | Nik Everett | 01 April 2019, 17:02:28 UTC | Docs: Drop inline callouts from the java API (#39932) (#40694) There is a single example in the Java API docs that contains an inline callout that is incompatible with Asciidoctor: ``` client.prepareUpdate("ttl", "doc", "1") .setScript(new Script( "ctx._source.gender = \"male\"" <1> , ScriptService.ScriptType.INLINE, null, null)) .get(); ``` This rewrites the example to use an Asciidoctor compatible end of line callout. It also looks nicer to me because it fits better on the page. ``` client.prepareUpdate("ttl", "doc", "1") .setScript(new Script( "ctx._source.gender = \"male\"", <1> ScriptService.ScriptType.INLINE, null, null)) .get(); ``` | 01 April 2019, 17:02:28 UTC |
| 822570e | Andrei Stefan | 01 April 2019, 15:10:51 UTC | SQL: have LIKE/RLIKE use wildcard and regexp queries (#40628) * Have LIKE and RLIKE only use term-level queries (wildcard and regexp respectively). They are already working only with exact fields, thus be in-line with how SQL works in general (what you index is what you search on). (cherry picked from commit 1bba887d481b49db231a1442922f1813952dcc67) | 01 April 2019, 16:36:31 UTC |
| 6759841 | Andrei Stefan | 01 April 2019, 15:01:03 UTC | SQL: Documentation for LIKE and RLIKE operators (#40623) (cherry picked from commit 9536c5f7b7fecda4592f6b169adef180eadbba54) | 01 April 2019, 16:36:30 UTC |
| 5480017 | Andrei Stefan | 01 April 2019, 14:34:54 UTC | Add JDBC trustore type to the docs (#40592) (cherry picked from commit cafde31129d85d20f9e445be131c9e85163bed9d) | 01 April 2019, 16:36:30 UTC |
| fc2ecb4 | Jason Tedor | 01 April 2019, 16:28:14 UTC | Add notable release highlights for 7.0 (#40481) This commit adds notable release highlights for 7.0. | 01 April 2019, 16:28:15 UTC |
| 6b7a607 | David Roberts | 01 April 2019, 13:20:01 UTC | [TEST] Mute WebhookHttpsIntegrationTests.testHttps Due to https://github.com/elastic/elasticsearch/issues/35503 | 01 April 2019, 13:25:51 UTC |
| fa6b4f3 | James Rodewig | 01 April 2019, 12:47:26 UTC | [DOCS] Add 'time value' links to several monitor settings (#40633) (#40687) | 01 April 2019, 12:47:26 UTC |
| 7e3e46c | Andrey Ershov | 01 April 2019, 08:49:05 UTC | Do not perform cleanup if Manifest write fails with dirty exception (#40519) Currently, if Manifest write is unsuccessful (i.e. WriteStateException is thrown) we perform cleanup of newly created metadata files. However, this is wrong. Consider the following sequence (caught by CI here https://github.com/elastic/elasticsearch/issues/39077): - cluster global data is written **successful** - the associated manifest write **fails** (during the fsync, ie files have been written) - deleting (revert) the manifest files, **fails**, metadata is therefore persisted - deleting (revert) the cluster global data is **successful** In this case, when trying to load metadata (after node restart because of dirty WriteStateException), the following exception will happen ``` java.io.IOException: failed to find global metadata [generation: 0] ``` because the manifest file is referencing missing global metadata file. This commit checks if thrown WriteStateException is dirty and if its we don't perform any cleanup, because new Manifest file might be created, but its deletion has failed. In the future, we might add more fine-grained check - perform the clean up if WriteStateException is dirty, but Manifest deletion is successful. Closes https://github.com/elastic/elasticsearch/issues/39077 (cherry picked from commit 1fac56916bb3c4f3333c639e59188dbe743e385b) | 01 April 2019, 09:51:46 UTC |
| ea9b53a | Jason Tedor | 01 April 2019, 02:10:45 UTC | Remove mention of soft deletes from getting started (#40668) We no longer need to mention soft deletes in the getting started guide now that retention leases exist and default to 12h. This commit removes mention of soft deletes from the getting started guide, to simplify that content. | 01 April 2019, 02:11:16 UTC |
| 7e5c520 | Jason Tedor | 31 March 2019, 23:42:22 UTC | Fix bug in detecting use of bundled JDK on macOS This commit fixes a bug in detecting the use of the bundled JDK on macOS. This bug arose because the path of Java home is different on macOS. | 31 March 2019, 23:43:24 UTC |
| 1901154 | Henning Andersen | 29 March 2019, 23:43:15 UTC | Reindex conflicts clarification (docs) (#40442) Made it more clear that conflicts : proceed only affects version conflicts. | 31 March 2019, 12:15:16 UTC |
| 60b36e1 | Marios Trivyzas | 30 March 2019, 15:56:44 UTC | SQL: [Tests] Enable integration tests for fixed issues (#40664) Enable some Ignored integration tests for issues/features that have already been resolved/implemented. (cherry picked from commit c23580f477ffc61c5701e14a91006db7bf21a8d4) | 30 March 2019, 15:57:38 UTC |
| 631cef1 | Mayya Sharipova | 30 March 2019, 14:56:23 UTC | Add information about the default sort mode (#40657) | 30 March 2019, 15:00:34 UTC |
| 630b4ac | Marios Trivyzas | 30 March 2019, 11:41:58 UTC | SQL: [Docs] Fix example for CURDATE Follows: 3dd0384d683940871f5d061f153b70c0420150fa (cherry picked from commit 35d731754455ec91e20190a874592a740c66aa44) | 30 March 2019, 11:45:58 UTC |
| b6416ba | Marios Trivyzas | 30 March 2019, 11:05:15 UTC | SQL: [Docs] Fix doc errors regarding CURRENT_DATE. (#40649) Some parts wrongly refered to CURRENT_TIMESTAMP. (cherry picked from commit 3dd0384d683940871f5d061f153b70c0420150fa) | 30 March 2019, 11:20:40 UTC |
| 6fca1a5 | Christoph Büscher | 29 March 2019, 22:38:37 UTC | Clarify using time_zone and date math in range query (#40655) Currently, the docs correctly state that using `now` in range queries will not be affected by the `time_zone` parameter. However, using date math roundings like e.g. `now\d` will be affected by the `time_zone`. Adding this example because it seems to be a frequently asked question and source of confusion. Relates to #40581 | 29 March 2019, 22:39:52 UTC |
| ac90d77 | Ryan Ernst | 29 March 2019, 21:20:53 UTC | Add notice for bundled jdk (#40576) * Add notice for bundled jdk This commit adds the license/notice for the bundled openjdk. * First draft * iteration * Fix package notices * Iteration * One more iteration | 29 March 2019, 21:21:33 UTC |
| 8d2767b | Ryan Ernst | 29 March 2019, 20:24:08 UTC | disable kerberos test until kerberos fixture is working again | 29 March 2019, 20:40:19 UTC |
| e041ddb | David Roberts | 29 March 2019, 16:40:25 UTC | [DOCS] Use "source" instead of "inline" in ML docs (#40635) Specifying an inline script in an "inline" field was deprecated in 5.x. The new field name is "source". (Since 6.x still accepts "inline" I will only backport this docs change as far as 7.0.) | 29 March 2019, 17:31:01 UTC |
| 7722f53 | Henning Andersen | 29 March 2019, 16:30:08 UTC | Unmute and fix testSubParserArray (#40626) testSubParserArray failed, fixed and improved to not always have an object as outer-level inside array. Closes #40617 | 29 March 2019, 16:53:54 UTC |
| 0fd8a9f | Henning Andersen | 28 March 2019, 17:55:31 UTC | Geo Point parse error fix (#40447) When geo point parsing threw a parse exception, it did not consume remaining tokens from the parser. This in turn meant that indexing documents with malformed geo points into mappings with ignore_malformed=true would fail in some cases, since DocumentParser expects geo_point parsing to end on the END_OBJECT token. Related to #17617 | 29 March 2019, 16:53:54 UTC |
| cb0e8dd | Luca Cavanna | 27 March 2019, 16:30:05 UTC | Increase suite timeout to 30 minutes for docs tests (#40521) I have been hitting the suite timeout on `DocsClientYamlTestSuiteIT` As far as I can see, the docs tests are taking quite a while, I assume it's because more and more docs snippets get added over time, which means more tests. The current suite timeout is the default 20 minutes. It takes me just a little less than 20 minutes to run these on my laptop. On my CI, I end up hitting the suite timeout. Hereby I propose that we increase the suite timeout to 30 minutes. | 29 March 2019, 16:07:24 UTC |
| 16e8086 | Alpar Torok | 29 March 2019, 14:46:55 UTC | Fix repository-hdfs when no docker and unnecesary fixture The hdfs-fixture is actually executed in plugin/repository-hdfs as a dependency. The fixture is not needed and actually causes a failure because we have two copies now and both use the same ports. | 29 March 2019, 14:52:37 UTC |
| 66c69d0 | Alpar Torok | 29 March 2019, 12:13:18 UTC | Avoid building hdfs-fixure use an image that works instead Avoid the additional requirement for the debian package repos to be up, and depend on dockerhub only instead. | 29 March 2019, 14:52:32 UTC |
| 0348d8e | Jason Tedor | 29 March 2019, 14:44:08 UTC | Fix more broken links in plugins docs The archive docs were moved around a bit, and this commit fixes another broken link in the plugins docs. | 29 March 2019, 14:44:59 UTC |
| ceabf77 | Jason Tedor | 29 March 2019, 14:18:59 UTC | Fix archives links in plugins docs This commit fixes some broken links to the archive layouts in the plugins docs. | 29 March 2019, 14:20:17 UTC |
| 0b24e11 | Ioannis Kakavas | 28 March 2019, 15:35:33 UTC | Disable integTest when Docker is not available (#40585) * Disable integTest when Docker is not available Resolves: #40549 | 29 March 2019, 14:17:53 UTC |
| a497aba | Ryan Ernst | 29 March 2019, 13:04:46 UTC | Add docs for bundled jdk (#40487) This commit changes the note in docs about required java version to note the existence of the bundled jdk and how to bring your own java. It also reorganizes the zip/targz docs as zip is no longer suitable on Linux/MacOS. | 29 March 2019, 13:08:49 UTC |
| 424ebfc | James Rodewig | 29 March 2019, 12:32:14 UTC | [DOCS] Correct keystore commands for Email and Jira actions in Watcher (#40417) (#40613) | 29 March 2019, 12:32:14 UTC |
| 1122411 | Jason Tedor | 29 March 2019, 12:24:52 UTC | Add usage indicators for the bundled JDK (#40616) This commit adds indications whether or not a distribution is from the bundled JDK, and whether or not we are using the bundled JDK. | 29 March 2019, 12:26:54 UTC |
| 9ee474a | Alpar Torok | 29 March 2019, 10:07:02 UTC | Add ability to mute and mute flaky fixture (#40630) | 29 March 2019, 11:16:25 UTC |
| 614e5d1 | Alpar Torok | 28 March 2019, 15:23:40 UTC | Test fixtures krb5 (#40297) Replaces the vagrant based kerberos fixtures with docker based test fixtures plugin. The configuration is now entirely static on the docker side and no longer driven by Gradle, also two different services are being configured since there are two different consumers of the fixture that can run in parallel and require different configurations. | 29 March 2019, 11:12:32 UTC |
| e3bb771 | Jim Ferenczi | 29 March 2019, 08:34:51 UTC | Update docs for the DFR similarity (#40579) The basic models `b, de, p` and the after effect `no` are not available anymore in Lucene 8 but they are still listed in the >7x documentation. This change removes these references that should also be listed in the breaking change of es 7.0. Closes #40264 | 29 March 2019, 09:44:44 UTC |
| 97d4eb6 | Martijn van Groningen | 29 March 2019, 08:44:42 UTC | Update ingest jdocs that a null return value will drop the current document. (#40359) | 29 March 2019, 08:48:09 UTC |
| 0ea67aa | James Rodewig | 28 March 2019, 19:00:41 UTC | [DOCS] Document common settings for snapshot repository plugins (#40475) (#40607) | 28 March 2019, 19:00:41 UTC |
| 3f05186 | lcawl | 28 March 2019, 17:03:40 UTC | [DOCS] Fixes formatting in breaking changes | 28 March 2019, 17:04:33 UTC |
| bf067ad | Lee Hinman | 28 March 2019, 16:42:28 UTC | Handle null retention leases in WaitForNoFollowersStep (#40477) In some cases the retention leases can return null, causing a `NullPointerException` when waiting for no followers. This wraps those so that no NPE is thrown. Here is an example failure: ``` [2019-03-26T09:24:01,368][ERROR][o.e.x.i.IndexLifecycleRunner] [node-0] policy [deletePolicy] for index [ilm-00001] failed on step [{"phase":"delete","action":"delete","name":"wait-for-shard-history-leases"}]. Moving to ERROR step java.lang.NullPointerException: null at org.elasticsearch.xpack.core.indexlifecycle.WaitForNoFollowersStep.lambda$evaluateCondition$0(WaitForNoFollowersStep.java:60) ~[?:?] at java.util.stream.ReferencePipeline$7$1.accept(ReferencePipeline.java:267) ~[?:1.8.0_191] at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) ~[?:1.8.0_191] at java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958) ~[?:1.8.0_191] at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) ~[?:1.8.0_191] at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498) ~[?:1.8.0_191] at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485) ~[?:1.8.0_191] at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) ~[?:1.8.0_191] at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:230) ~[?:1.8.0_191] at java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:196) ~[?:1.8.0_191] at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) ~[?:1.8.0_191] at java.util.stream.ReferencePipeline.anyMatch(ReferencePipeline.java:449) ~[?:1.8.0_191] at org.elasticsearch.xpack.core.indexlifecycle.WaitForNoFollowersStep.lambda$evaluateCondition$2(WaitForNoFollowersStep.java:61) ~[?:?] at org.elasticsearch.action.ActionListener$1.onResponse(ActionListener.java:62) ~[elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT] at org.elasticsearch.action.support.ContextPreservingActionListener.onResponse(ContextPreservingActionListener.java:43) ~[elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT] at org.elasticsearch.action.support.TransportAction$1.onResponse(TransportAction.java:68) ~[elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT] at org.elasticsearch.action.support.TransportAction$1.onResponse(TransportAction.java:64) ~[elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT] at org.elasticsearch.action.support.ContextPreservingActionListener.onResponse(ContextPreservingActionListener.java:43) ~[elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT] at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction$AsyncAction.onCompletion(TransportBroadcastByNodeAction.java:383) ~[elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT] at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction$AsyncAction.onNodeResponse(TransportBroadcastByNodeAction.java:352) ~[elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT] at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction$AsyncAction$1.handleResponse(TransportBroadcastByNodeAction.java:324) ~[elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT] at org.elasticsearch.action.support.broadcast.node.TransportBroadcastByNodeAction$AsyncAction$1.handleResponse(TransportBroadcastByNodeAction.java:314) ~[elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT] at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleResponse(TransportService.java:1095) ~[elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT] at org.elasticsearch.transport.TransportService$DirectResponseChannel.processResponse(TransportService.java:1176) ~[elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT] ... ``` | 28 March 2019, 16:49:25 UTC |
| 9c9694d | Gordon Brown | 28 March 2019, 16:34:14 UTC | Correct ILM metadata minimum compatibility version (#40569) The ILM metadata minimum compatibility version was not set correctly, which can cause issues in mixed-version clusters. | 28 March 2019, 16:34:14 UTC |
| 2964cea | Tanguy Leroux | 27 February 2019, 16:54:54 UTC | Mute SpecificMasterNodesIT.testElectOnlyBetweenMasterNodes() Tracked in #38331 | 28 March 2019, 14:21:42 UTC |
| 513fef0 | Yannick Welsch | 28 March 2019, 13:01:11 UTC | Mute testHttpInput Relates #40587 | 28 March 2019, 13:06:16 UTC |
| 99e7c42 | Andrei Stefan | 28 March 2019, 12:28:07 UTC | Include functions' aliases in the list of functions (#40584) (cherry picked from commit 4034f8f31616353d2f5d09a90753d75e2870ee18) | 28 March 2019, 12:51:25 UTC |
| 8c7015d | David Turner | 28 March 2019, 12:13:25 UTC | Optimise rejection of out-of-range `long` values (#40325) Today if you try and insert a very large number like `1e9999999` into a long field we first construct this number as a `BigDecimal`, convert this to a `BigInteger` and then reject it because it is out of range. Unfortunately making such a large `BigInteger` is rather expensive. We can avoid this expense by performing a (weaker) range check on the `BigDecimal` representation of incoming `long`s too. Relates #26137 Closes #40323 | 28 March 2019, 12:28:21 UTC |
| 7cb9ae7 | David Turner | 28 March 2019, 12:09:31 UTC | Add docs for cluster.remote.*.proxy setting (#40281) In #33062 we introduced the `cluster.remote.*.proxy` setting for proxied connections to remote clusters, but left it deliberately undocumented since it needed followup work so that it could work with SNI. However, since #32517 is now closed we can add this documentation and remove the comment about its lack of documentation. | 28 March 2019, 12:11:44 UTC |
| fe449ca | Yannick Welsch | 28 March 2019, 11:12:07 UTC | Mute WatchAckTests.testAckAllActions Relates to #35506 | 28 March 2019, 11:13:56 UTC |
| 075e342 | Adrien Grand | 28 March 2019, 10:59:37 UTC | Deprecate types in `_graph/explore` calls. (#40466) (#40515) Any call that uses a path that sets a type will trigger a deprecation warning. | 28 March 2019, 10:59:37 UTC |
| 19d2f16 | jimczi | 28 March 2019, 08:55:29 UTC | Fix SearchResponseMerger#testMergeSearchHits This commit fixes an edge case in tests where search hits are empty after the merge but some shards returned hits. This can happen if the total number of merged hits is less than the provided `from`. Closes #40553 | 28 March 2019, 08:57:56 UTC |
| f2ec4a2 | Andrei Stefan | 28 March 2019, 08:11:23 UTC | SQL: add "fuzziness" option to QUERY and MATCH function predicates (#40529) * Remove unused "locale" and "lowercase_expanded_terms" options from QUERY. (cherry picked from commit c122fc6edddbb99c73ce25168d1152409c0b7892) | 28 March 2019, 08:38:07 UTC |
| 9a79179 | Adrien Grand | 28 March 2019, 08:31:53 UTC | Remove type from VersionConflictEngineException. (#37490) (#40516) It initially mentioned the type in the exception because the type used to be required to uniquely identify a document. This is not necessary anymore given that indices have at most one type. | 28 March 2019, 08:31:53 UTC |
| 7a24f3d | Andrei Stefan | 27 March 2019, 15:18:14 UTC | SQL: MATCH and QUERY documentation; one list of functions (#40494) * Document MATCH and QUERY function predicates. * Polish the functions pages and add a list of functions to the main Functions & Operators page. (cherry picked from commit 4cec0ae1b962ec7ea011a290aec72740386eb808) | 28 March 2019, 05:00:56 UTC |
| cfa5319 | Jason Tedor | 27 March 2019, 20:39:24 UTC | Mark notable breaking changes for 7.0 (#40478) This commit adds a tag for each breaking change that could be considered notable. | 27 March 2019, 20:39:24 UTC |
| f63766d | Benjamin Trent | 27 March 2019, 19:52:04 UTC | Muting test for #40553 (#40556) | 27 March 2019, 19:52:04 UTC |
| a21ba2c | Julie Tibshirani | 27 March 2019, 18:13:51 UTC | Fix an off-by-one error in the vector field dimension limit. (#40489) Previously only vectors up to 499 dimensions were accepted, whereas the stated limit is 500. | 27 March 2019, 18:28:56 UTC |
| 78d6867 | Yannick Welsch | 27 March 2019, 17:48:35 UTC | Use default discovery implementation for single-node discovery (#40036) Switches "discovery.type: single-node" from using a separate implementation for single-node discovery to using the existing standard discovery implementation, with two small adaptions: - auto-bootstrapping, but requiring initial_master_nodes not to be set. - not actively pinging other nodes using the Peerfinder - not allowing other nodes to join its single-node cluster (if they have e.g. been set up using regular discovery and connect to the single-disco node). | 27 March 2019, 18:04:47 UTC |
| e39e40b | Marios Trivyzas | 27 March 2019, 16:13:18 UTC | SQL: Fix getTime() methods in JDBC (#40484) Previously, `getTime(colIdx/colLabel)` and `getObject(colIdx/colLabel, java.sql.Time.class)` methods were computing the time from a `ZonedDateTime` by applying day in millis modulo on the epoch millis of the `ZonedDateTime` object. This is wrong as we need to keep the time related fields at the timezone of the `ZonedDateTime` object and just set the date info to the epoch date (01/01/1970). Additionally fixes a testing issue as the original timezone id is converted to an offset string when parsing the response from the server. | 27 March 2019, 16:56:29 UTC |
| 4f231ee | lcawl | 27 March 2019, 16:37:46 UTC | [DOCS] Removes coming tags | 27 March 2019, 16:37:46 UTC |
| bc8fd56 | David Turner | 27 March 2019, 15:49:12 UTC | Stabilise testStaleMasterNotHijackingMajority (#40253) This test inadvertently asserts that the election occurs after a master failure is clean. However, messy elections are a fact of life so we should not fail on a messy election. This change moves this test away from an `AbstractDisruptionTestCase` since it does not need the fault detector to be so enthusiastic, and weakens the assertions to merely say that we ignore states published by the old master without saying anything about the cleanliness of the election. Closes #36556 | 27 March 2019, 16:19:40 UTC |
| 90a7d07 | lcawl | 27 March 2019, 16:02:01 UTC | [DOCS] Updates version to 7.0.0-rc1 | 27 March 2019, 16:02:01 UTC |
| b3d1f82 | David Turner | 27 March 2019, 15:56:02 UTC | Mention legacy discovery settings in migration doc (#40528) Today the upgrade assistant identifies that discovery configuration is required in production mode, but links to docs saying to add one of these settings: - `discovery.seed_hosts` - `discovery.seed_providers` - `cluster.initial_master_nodes` However these settings do not exist in 6.7 so this is unhelpful advice. This commit adjusts the docs to give more useful advice to users arriving at this page from the upgrade assistant. Relates https://discuss.elastic.co/t/174102 | 27 March 2019, 15:55:39 UTC |
| 43892ce | Benjamin Trent | 27 March 2019, 14:16:06 UTC | Muting watcher tests for issue #35503 (#40527) * Muting watcher tests for issue #35503 * blocking the two troublsome suites | 27 March 2019, 14:35:24 UTC |
| 5be8b84 | James Rodewig | 27 March 2019, 14:31:23 UTC | Deprecate elasticsearch.yml as supported Slack config method (#40410) | 27 March 2019, 14:33:33 UTC |
| ee4ad1e | James Rodewig | 27 March 2019, 14:02:37 UTC | Fix typo in rollup_index definition (#40520) | 27 March 2019, 14:06:01 UTC |
| 153de9b | michaelbaamonde | 27 March 2019, 13:17:09 UTC | Add release notes for 7.0.0-rc1. (#40479) * Add release notes for 7.0.0-rc1. * [DOCS] Fixes broken link to breaking changes * [DOCS] Removed old ML PRs; edited titles * Remove superseded PR. * Clean up Lucene upgrade PRs/issues. | 27 March 2019, 13:17:09 UTC |
| 63d3fa7 | Przemyslaw Gomulka | 27 March 2019, 12:52:09 UTC | Parse composite patterns using ClassicFormat.parseObject backport(#40100) (#40502) Java-time fails parsing composite patterns when first pattern matches only the prefix of the input. It expects pattern in longest to shortest order. Because of this constructing just one DateTimeFormatter with appendOptional is not sufficient. Parsers have to be iterated and if the parsing fails, the next one in order should be used. In order to not degrade performance parsing should not be throw exceptions on failure. Format.parseObject was used as it only returns null when parsing failed and allows to check if full input was read. closes #39916 backport #40100 | 27 March 2019, 12:52:09 UTC |
| ed9ae00 | James Rodewig | 27 March 2019, 12:36:15 UTC | [Docs] Fix command to save SMTP password for email account (#40444) (#40453) | 27 March 2019, 12:36:15 UTC |
| e147683 | Costin Leau | 27 March 2019, 10:20:16 UTC | SQL: Update JDBC class name in client screenshots (cherry picked from commit 79a3b93deb858961ecbe4516ed9d8f209016666f) | 27 March 2019, 10:22:35 UTC |
| 8bc2df6 | Jim Ferenczi | 27 March 2019, 10:15:25 UTC | Fix random failures in SearchResponseMerger#testMergeSearchHits (#40223) This commit fixes the expectation in the test when the search hits are empty. Closes #40214 | 27 March 2019, 10:17:42 UTC |
| 441a67b | Dimitrios Liappis | 27 March 2019, 08:21:26 UTC | Wrap Dockerfile yum operations in retries (#40462) While yum does retry retrieving files 10 times by default [1], slow network fetches, governed by `minrate` cause immediate aborts without getting retried. Wrap yum commands in a 10 iteration retry loop. [1] http://man7.org/linux/man-pages/man5/yum.conf.5.html Backport of #40349 | 27 March 2019, 08:21:26 UTC |
| 7f76835 | lcawl | 26 March 2019, 22:45:53 UTC | [DOCS] Adds anchors and x-pack icons for frozen indices | 26 March 2019, 22:58:28 UTC |
| a04c27e | Jason Tedor | 26 March 2019, 22:47:57 UTC | Add more Java 12 distributions to testing (#40482) This commit adds the Oracle JDK 12 and the Zulu JDK 12 distributions to testing. | 26 March 2019, 22:48:55 UTC |
| e6a805b | Julie Tibshirani | 26 March 2019, 20:08:08 UTC | Stop clearing all watches in watcher integration tests. (#39724) | 26 March 2019, 20:37:42 UTC |
| 261e3fe | Ryan Ernst | 26 March 2019, 18:41:22 UTC | Delete jdk extract dir before extracting (#40471) This commit first deletes the directory we extract the bundled jdk into in order to make gradle's copy task happy. | 26 March 2019, 18:43:34 UTC |
| 2cd699e | Jay Modi | 26 March 2019, 14:40:00 UTC | Use ephemeral ports for idp-fixture (#40333) This change removes the use of hardcoded port values for the idp-fixture in favor of the mapped ephemeral ports. This should prevent failures due to port conflicts in CI. | 26 March 2019, 18:02:58 UTC |
| a74885b | Daniel Mitterdorfer | 26 March 2019, 16:37:35 UTC | Add version 6.7.1 | 26 March 2019, 16:37:47 UTC |
| 1c8ac96 | Yannick Welsch | 26 March 2019, 16:00:28 UTC | Remove timeout task after completing cluster state publication (#40411) Each cluster state publication schedules a cancellation task with the provided publication timeout (30s by default). This scheduled cancellation keeps a reference to the publication, and therefore the full cluster state that was published. In case of frequently updating a large cluster state, this results in a large number of cancellation tasks keeping references to all previously published cluster states. | 26 March 2019, 16:20:17 UTC |
| 3cd3f22 | Henning Andersen | 26 March 2019, 14:11:51 UTC | Store Pending Deletions Fix (#40345) FilterDirectory.getPendingDeletions does not delegate, fixed temporarily by overriding in StoreDirectory. This in turn caused duplicate file name use after a trimUnsafeCommits had been done, since a new IndexWriter would not consider the pending deletes in IndexFileDeleter. This should only happen on windows (AFAIK). Reenabled doing index updates for all tests using IndexShardTests.indexOnReplicaWithGaps (which could fail due to above when using mocked WindowsFS). Added getPendingDeletions delegation to all elasticsearch FilterDirectory subclasses that were not trivial test-only overrides to minimize the risk of hitting this issue in another case. | 26 March 2019, 14:32:08 UTC |
| 3ea8e21 | Adrien Grand | 26 March 2019, 13:22:59 UTC | Enhancements to IndicesQueryCache. (#39099) (#40445) This commit adds the following: - more tests to IndicesServiceCloseTests, one of them found a bug in the order in which `IndicesQueryCache#onClose` and `IndicesService.indicesRefCount#decRef` are called. - made `IndicesQueryCache.stats2` a synchronized map. All writes to it are already protected by the lock of the Lucene cache, but the final read from an assertion in `IndicesQueryCache#close()` was not so this change should avoid any potential visibility issues. - human-readable `toString`s to make debugging easier. Relates #37117 | 26 March 2019, 13:22:59 UTC |
| 4b387f6 | Alpar Torok | 26 March 2019, 10:18:21 UTC | Add Gradle init script to configure artifactoy (#40412) The script will be use in CI to configure our own Artifactory instance so CI does not depend on external network resources nor do we generate excessive load on these resources. In case the repo is not accessible Gradle should fall back to using the public ones. | 26 March 2019, 10:22:41 UTC |
| 3c8c9ec | Ed Savage | 25 March 2019, 11:55:04 UTC | [ML][TEST] Fix failing test testPersistJobOnGracefulShutdown_givenTimeAdvancedAfterNoNewData (#40363) Ensure that there is at least a 1s delay between the time that state is persisted by each of the two jobs in the test. Model snapshot IDs use the current time in epoch seconds to distinguish themselves, hence snapshots will be overwritten by another if it occurs in the same 1s window. Closes #40347 | 26 March 2019, 08:50:34 UTC |
| f1edfa3 | Armin Braun | 26 March 2019, 08:00:01 UTC | Use Correct Enum in Wipe Snapshots Test Method (#40422) (#40439) * Mistake was made in #39662 * The response deserialized here is `org.elasticsearch.action.admin.cluster.snapshots.get.GetSnapshotsResponse` which uses `org.elasticsearch.snapshots.SnapshotInfo` which uses `org.elasticsearch.snapshots.SnapshotState` and not the shard state | 26 March 2019, 08:00:01 UTC |
| 3499078 | Lisa Cawley | 25 March 2019, 17:23:10 UTC | [DOCS] Simplify ML upgrade step (#40006) | 25 March 2019, 17:34:50 UTC |
| 2367c49 | James Rodewig | 25 March 2019, 13:03:07 UTC | Update Windows command to support prettified json licenses (#40408) | 25 March 2019, 13:03:07 UTC |
| d604ae9 | aladdam | 20 March 2019, 15:19:32 UTC | [DOCS] match description with example in allocation docs page (#39606) | 25 March 2019, 09:30:14 UTC |
| cc7680c | Armin Braun | 24 March 2019, 18:09:06 UTC | Log Warning on Failed Blob Deletes in BlobStoreRepository (#40188) (#40341) * Log Warning on Failed Blob Deletes in BlobStoreRepository * We should not just debug log these spots, they all can and will lead to leaked files when snapshot deletion fails | 24 March 2019, 18:09:06 UTC |
| 3171bef | Jason Tedor | 23 March 2019, 16:55:48 UTC | Update feature aware check ASM to 7.1 (#40389) This commit updates the feature aware check ASM dependency to ASM 7.1. This gives us JDK 13 compatibility. | 23 March 2019, 16:57:31 UTC |
| 6766104 | Marios Trivyzas | 23 March 2019, 15:59:19 UTC | SQL: Fix issue timezone issues with JDBC getDate/getTime (#40360) Previously, `getDate(int columnIdx)/getDate(String columnLabel)` and were using legacy`java.util.Calendar` instead of the the `java.time.*` classes to reset to the start of day. This resulted in different results for certain timestamps and timezones when calling `getDate(col)` vs`getObject(col, java.sql.Date)` Now only the methods (that must be implemented due to the JDBC spec) `getDate(int columnIdx, Calendar cal)/getDate(String columnLabel, Calendar cal)` are still using the `java.util.Calendar` for those conversion. The same change was applied to `getTime(int columnIdx)/getTime(String columnLabel)` and `getTimestamp(int columnIdx)/getTimestamp(String columnLabel)` Fixes: #40289 (cherry picked from commit 44560671f18397e0c58e3647732880fcb73a5034) | 23 March 2019, 16:26:08 UTC |
| 46aeda9 | Marios Trivyzas | 23 March 2019, 13:11:32 UTC | SQL: Fix metric aggs on date/time to not return double (#40377) Previously metric aggregations on date fields would return a double which caused errors when trying to apply scalar functions on top, e.g.: ``` SELECT YEAR(MAX(date)) FROM test ``` Fixes: #40376 (cherry picked from commit 41d0a038467fbdbbf67fd9bfdf27623451cae63a) | 23 March 2019, 13:50:33 UTC |
| 9f1e8a9 | Jason Tedor | 23 March 2019, 13:38:49 UTC | Only run retention lease actions on active primary (#40386) In some cases, a request to perform a retention lease action can arrive on a primary shard before it is active. In this case, the primary shard would not yet be in primary mode, tripping an assertion in the replication tracker. Instead, we should not attempt to perform such actions on an initializing shard. This commit addresses this by not returning the primary shard in the single shard iterator if the primary shard is not yet active. | 23 March 2019, 13:39:49 UTC |
| daf97ce | Costin Leau | 23 March 2019, 10:41:51 UTC | SQL: Add missing handling of IP field in JDBC (#40384) Fix #40358 (cherry picked from commit ee286fa4893817637c05d72b93b254b36efc0dae) (cherry picked from commit d2296249499e31bd512390ac3d20bc38009612b3) | 23 March 2019, 10:59:02 UTC |
| 41eed00 | Andrei Stefan | 23 March 2019, 04:36:44 UTC | SQL: Fix RLIKE bug and improve testing for RLIKE statement (#40354) * Refactor RegexMatch to support both LIKE and RLIKE * Add integration tests for RLIKE * Polish the rest of tests (cherry picked from commit 7562d6eeeb77c04794002649fe726f4b3a9a398b) | 23 March 2019, 04:54:48 UTC |
