| c63e621 | Nhat Nguyen | 26 February 2020, 04:25:00 UTC | Revert "Fix testKeepTranslogAfterGlobalCheckpoint" This reverts commit 5f20e2eeda230cc47b21e4e742e941b1d529c052. | 26 February 2020, 04:25:00 UTC |
| a228778 | Lisa Cawley | 26 February 2020, 00:57:38 UTC | [DOCS] Fixes monitoring links (#52790) | 26 February 2020, 03:17:56 UTC |
| 5f20e2e | Nhat Nguyen | 25 February 2020, 16:46:43 UTC | Fix testKeepTranslogAfterGlobalCheckpoint Read the last synced global checkpoint after flushing as we might advance it during committing. CI: https://gradle-enterprise.elastic.co/s/7o6qengg4gva2 | 25 February 2020, 16:51:12 UTC |
| c1aed6f | Ioannis Kakavas | 25 February 2020, 09:58:50 UTC | Adjust file realm docs (#52471) (#52747) The existing wording in the file realm docs proved confusing for users as it seemed to indicate that it should _only_ be used as a fallback/recovery realm and that it is not a first class realm. This change attempts to clarify this and point out that recovery is _a_ use case for the file realm but not the only intended one. | 25 February 2020, 09:58:50 UTC |
| df1fa68 | Ioannis Kakavas | 25 February 2020, 09:56:49 UTC | [6.8] Update BouncyCastle to 1.64 (#52185) (#52711) * Update BouncyCastle to 1.64 (#52185) This commit upgrades the bouncycastle dependency from 1.61 to 1.64. | 25 February 2020, 09:56:49 UTC |
| f3cbeea | Jason Tedor | 22 February 2020, 14:09:04 UTC | Add messages for CCR on license state changes (#52470) When a license expires, or license state changes, functionality might be disabled. This commit adds messages for CCR to inform users that CCR functionality will be disabled when a license expires, or when license state changes to a license level lower than trial/platinum/enterprise. | 22 February 2020, 14:46:00 UTC |
| 3d64edc | Sean Story | 21 February 2020, 09:23:56 UTC | [Docs]: Fix typo 'Got' -> 'Go' (#52603) Fix typo 'Got' -> 'Go' (cherry picked from commit cf7eca270db964c9c474a70da647cb8396f677ba) | 21 February 2020, 09:27:47 UTC |
| 18739c6 | Valentin Crettaz | 19 February 2020, 17:26:47 UTC | [DOCS] Clarify that "now" cannot be used in `date_range` at index time (#52446) `date_range` fields do not accept `"now"` as a value of either bounds at indexing time. This corrects an error in the range data type mapping docs. | 19 February 2020, 17:36:57 UTC |
| f3839d8 | debadair | 18 February 2020, 20:41:05 UTC | [DOCS] Clean up links from SQL client app pages. (#52442) * [DOCS] Clean up links from SQL client app pages. * Linked to client apps from prereqs. | 18 February 2020, 21:00:02 UTC |
| 8969c85 | Nhat Nguyen | 17 February 2020, 20:05:42 UTC | Fix timeout in testDowngradeRemoteClusterToBasic (#52322) - ESCCRRestTestCase#ensureYellow does not work well with assertBusy - Increases timeout to 60s Closes #52036 | 17 February 2020, 22:40:46 UTC |
| 41731c1 | Jason Tedor | 16 February 2020, 22:21:28 UTC | Fix shard follow task cleaner under security (#52347) The shard follow task cleaner executes on behalf of the user to clean up a shard follow task after the follower index has been deleted. Otherwise, these persistent tasks are left laying around, and they fail to execute because the follower index has been deleted. In the face of security, attempts to complete these persistent tasks would fail. This is because these cleanups are executed under the system context (this makes sense, they are happening on behalf of the user after the user has executed an action) but the system role was never granted the permission for persistent task completion. This commit addresses this by adding this cluster privilege to the system role. | 16 February 2020, 22:31:28 UTC |
| 79a342e | OriGlassman | 14 February 2020, 18:41:51 UTC | [DOCS] Fixed "SeachRequest" -> "SearchRequest" typo in HLRC docs (#52144) | 14 February 2020, 18:44:00 UTC |
| bd77a21 | Carl Casbolt | 14 February 2020, 18:36:07 UTC | [DOCS] Add missing formatting to docker instructions (#51994) | 14 February 2020, 18:36:07 UTC |
| d80424f | Ioannis Kakavas | 14 February 2020, 08:25:29 UTC | [6.8] Update cryptacular to 1.2.4 (#52331) (#52351) Cryptacular is a dependency of opensaml | 14 February 2020, 08:25:29 UTC |
| 72d7546 | Marios Trivyzas | 13 February 2020, 19:11:04 UTC | [Tests] Update skip version for YAML tests (#52326) Update skip versions upper boundary to match the release or intended release version of the feature/fix. | 13 February 2020, 19:11:04 UTC |
| bb4862e | Marios Trivyzas | 12 February 2020, 20:53:26 UTC | SQL: [Docs] Fix typo Add missing closing "`" Follows: 6033c70f8c82288ffcf17758957c65c32c388cdf | 12 February 2020, 20:53:26 UTC |
| 85f1023 | Nhat Nguyen | 07 February 2020, 16:09:40 UTC | Increase shard inactive time to 1h in upgrade tests (#52051) Similar to the fix in #51651, this commit increases the shard inactive timeout for x-pack. Closes #52031 | 12 February 2020, 16:59:59 UTC |
| 6033c70 | Marios Trivyzas | 12 February 2020, 11:54:42 UTC | SQL: [Docs] Add limitation for sorting on aggs (#52210) Add a section to point out that when ordering by an aggregate only plain aggregate functions are allowed, no scalars/operators can be used on top of them. Fixes: #52204 (cherry picked from commit 78a1185549ff7f3229fd2d036567eb2a4f2cf230) | 12 February 2020, 11:57:43 UTC |
| 45ec73d | Marios Trivyzas | 12 February 2020, 08:37:36 UTC | SQL: Fix ORDER BY on aggregates and GROUPed BY fields (#51894) Previously, in the in-memory sorting module `LocalAggregationSorterListener` only the aggregate functions where used (grabbed by the `sortingColumns`). As a consequence, if the ORDER BY was also using columns of the GROUP BY clause, (especially in the case of higher priority - before the aggregate functions) wrong results were produced. E.g.: ``` SELECT gender, MAX(salary) AS max FROM test_emp GROUP BY gender ORDER BY gender, max ``` Add all columns of the ORDER BY to the `sortingColumns` so that the `LocalAggregationSorterListener` can use the correct comparators in the underlying PriorityQueue used to implement the in-memory sorting. Fixes: #50355 (cherry picked from commit be680af11c823292c2d115bff01658f7b75abd76) | 12 February 2020, 11:38:11 UTC |
| 6075a77 | Marios Trivyzas | 11 February 2020, 17:20:41 UTC | SQL: [Tests] Fix integration test Fix issue with VARCHAR display size (copied from 7.x) Follows: 4797347ae8f3d2024452d150e2b84da53b990de5 | 11 February 2020, 17:20:41 UTC |
| 4797347 | Marios Trivyzas | 11 February 2020, 13:59:06 UTC | SQL: [Tests] Add integ tests for timezone and pagination (#52101) Cherry pick and adapt tests to validate correct behaviour regarding processing of results that involve the use of the client configured timezone by the HitExtractors when paginating over the results of the query (use of cursors). (cherry picked from commit 8f7afbdeb9295999b48a6c36db5b31cbe0cee432) | 11 February 2020, 15:50:46 UTC |
| 3976770 | Mark Vieira | 10 February 2020, 21:49:44 UTC | Only pull docker images for fixture projects (#52157) | 10 February 2020, 21:58:52 UTC |
| 5b4987d | Mark Vieira | 10 February 2020, 19:16:15 UTC | Remove unnecessary CI configuration files Signed-off-by: Mark Vieira <portugee@gmail.com> | 10 February 2020, 19:18:25 UTC |
| c19aedf | Rory Hunter | 06 February 2020, 10:54:51 UTC | Clarify use of ES_JAVA_OPTS and Docker (#51987) Backport of #51867. Tweak the documentation around configuring the heap size when using Docker, to state that: - using `ES_JAVA_OPTS` is the preferred method - Any `ES_JAVA_OPTS` overrides the defaults in `jvm.options` - It's possible to bind-mount a custom `jvm.options` | 06 February 2020, 10:54:51 UTC |
| 00f0fc7 | Ioannis Kakavas | 06 February 2020, 06:50:53 UTC | Mute SecurityTribeTests (#51976) see: #49109 | 06 February 2020, 06:50:53 UTC |
| 050bdfc | Jason Tedor | 06 February 2020, 01:46:54 UTC | Log failure when cleaning shard follow task (#51971) When clenaing a shard follow task after an index has been deleted, an exception can occur submitting the complete persistent task action. However, this exception message is not logged. This commit addresses this by including the exception that led to the failure in the log message. | 06 February 2020, 01:48:14 UTC |
| 33a05e2 | Ioannis Kakavas | 05 February 2020, 16:23:10 UTC | Remove 8fips from our runtime matrix (#51934) The relevant handling part has been removed in infra, FIPS 140 testing needs to be enabled in the same manner as it happened for master and 7.x in #48378 and #49485 resolves: #51924 | 05 February 2020, 16:23:10 UTC |
| b59cff4 | Tim Vernum | 04 February 2020, 03:59:06 UTC | Preserve ApiKey credentials for async verification (#51845) The ApiKeyService would aggressively "close" ApiKeyCredentials objects during processing. However, under rare circumstances, the verfication of the secret key would be performed asychronously and may need access to the SecureString after it had been closed by the caller. The trigger for this would be if the cache already held a Future for that ApiKey, but the future was not yet complete. In this case the verification of the secret key would take place asynchronously on the generic thread pool. This commit moves the "close" of the credentials to the body of the listener so that it only occurs after key verification is complete. Backport of: #51244 | 04 February 2020, 03:59:06 UTC |
| 63a2253 | Marios Trivyzas | 03 February 2020, 23:40:40 UTC | SQL: Enhance detection of scalars on nested fields Enhance detection and validation of scalars on top of nested fields used in WHERE, HAVING and ORDER BY. Previously, in case of aliases or ordinal references the usage of scalars on nested fields was not detected. Follows: ea4504c495a87ddf95939027e882330c946f58c3 | 03 February 2020, 23:40:40 UTC |
| d197d7d | Sandeep Kanabar | 03 February 2020, 16:37:48 UTC | [DOCS] Update secure-settings.asciidoc (#51798) | 03 February 2020, 16:37:48 UTC |
| 3139a74 | Darren LaCasse | 31 January 2020, 18:27:37 UTC | [DOCS] Remove extra word (#51757) | 31 January 2020, 18:33:44 UTC |
| 9706ced | David Turner | 31 January 2020, 12:29:58 UTC | Note that shards of closed indices may be ignored (#50596) Fixes #42334 | 31 January 2020, 12:29:58 UTC |
| 400b72a | Nhat Nguyen | 30 January 2020, 14:02:38 UTC | Increase shard inactive time to 1h in upgrade tests (#51651) testRecovery relies on the fact that shards are not flushed on inactive. Our CI recently was too slow. It took more than 20 minutes to complete the full cluster restart suite. This slowness caused some shards of testRecovery were flushed on inactive. This commit increases the inactive time to 1h to reduce this noise. Closes #51640 | 31 January 2020, 03:01:14 UTC |
| bbd168f | Nhat Nguyen | 29 January 2020, 21:27:33 UTC | Force flush in FrozenEngine#testSearchers (#51635) We need to force flush to make the last commit safe; otherwise, we might fail to open FrozenEngine. Note that we force flush before closing a shard. Closes #51620 | 31 January 2020, 03:00:29 UTC |
| ea4504c | Marios Trivyzas | 30 January 2020, 13:48:34 UTC | SQL: Fix ORDER BY YEAR() function (#51562) Previously, if YEAR() was used as and ORDER BY argument without being wrapped with another scalar (e.g. YEAR(birth_date) + 10), no script ordering was used but instead the underlying field (e.g. birth_date) was used instead as a performance optimisation. This works correctly if YEAR() is the only ORDER BY arg but if further args are used as tie breakers for the ordering wrong results are produced. This is because 2 rows with the different birth_date but on the same year are not tied as the underlying ordering is on birth_date and not on the YEAR(birth_date), and the following ORDER BY args are ignored. Remove this optimisation for YEAR() to avoid incorrect results in such cases. As a consequence another bug is revealed: scalar functions on top of nested fields produce scripted sorting/filtering which is not yet supported. In such cases no error was thrown but instead all values for such nested fields were null and were passed to the script implementing the sorting/filtering, producing incorrect results. Detect such cases and throw a validation exception. Fixes: #51224 (cherry picked from commit f41efd6753dc3650a7eabb3e07b02b3b32c5704c) | 30 January 2020, 17:19:34 UTC |
| 52107ed | Marios Trivyzas | 30 January 2020, 14:49:43 UTC | SQL: Verify Full-Text Search functions not allowed in SELECT (#51568) (#51673) Add a verification that full-text search functions `MATCH()` and `QUERY()` are not allowed in the SELECT clause, so that a nice error message is returned to the user early instead of an "ugly" exception. Fixes: #47446 (cherry picked from commit 65ad2699c63fdf9509de3e4ec894037d369ea179) | 30 January 2020, 14:49:43 UTC |
| fe254a2 | Andrei Stefan | 29 January 2020, 14:54:55 UTC | SQL: improve timezone sensitive JDBC tests to account for offset differences (#51592) * Changed one test to use fixed offsets * Changed several tests to compare only the relevant parts of the conversion failure error message and ignore the actual datetime String from the error message itself | 29 January 2020, 14:54:55 UTC |
| e89ec30 | Nhat Nguyen | 29 January 2020, 03:04:49 UTC | Fix missing import in SQL with SSL tests build | 29 January 2020, 03:04:49 UTC |
| fc6fc73 | Jason Tedor | 29 January 2020, 01:23:40 UTC | Fix imports in SQL with SSL tests build This commit fixes another import that was lost on a backport gone bad. The imports were not needed in master, but still needed in 6.8. | 29 January 2020, 01:23:49 UTC |
| 886318f | Jason Tedor | 28 January 2020, 23:48:56 UTC | Fix compilation in SQL with SSL tests build This commit fixes a compilation issue that occurred after some imports were no longer needed in master, but still needed here, so got removed when a commit was backported. | 28 January 2020, 23:48:56 UTC |
| 79be5a1 | Jason Tedor | 28 January 2020, 23:44:06 UTC | Ignore virtual ethernet devices that disappear (#51581) When checking if a device is up, today we can run into virtual ethernet devices that disappear while we are in the middle of checking. This leads to "no such device". This commit addresses such devices by treating them as not being up, if they are virtual ethernet devices that disappeared while we were checking. | 28 January 2020, 23:45:04 UTC |
| ab0f0dc | Jason Tedor | 28 January 2020, 23:38:02 UTC | Check if interface is up for loopback devices only (#51583) In the SQL with SSL tests, we need to find the interfaces that are up, are loopback devices, or have a loopback address. If we check if the device is up first, we can run into situations where the device is a virtual ethernet device that might have disappeared between us seeing the device, and checking if it is up. By first checking if the device is a loopback device or it has a loopback address, then we can avoid checking if the device is up except for loopback devices and therefore we can avoid the disappearing virtual ethernet device problem. | 28 January 2020, 23:39:10 UTC |
| c97361f | Armin Braun | 19 June 2019, 11:50:26 UTC | Fix NetworkUtilsTests (#43295) * Follow up to #42109: * Adjust test to only check that interface lookup by name works not actually lookup IPs which is brittle since virtual interfaces can be destroyed/created by Docker while the tests are running Co-authored-by: Jason Tedor <jason@tedor.me> | 28 January 2020, 21:44:23 UTC |
| 25df798 | Jason Tedor | 28 January 2020, 21:43:21 UTC | Add optional matchers to test framework This commit adds some optional matchers to the test framework, which helps keep assertions around the use of matchers clean. | 28 January 2020, 21:44:22 UTC |
| 6f4a3b3 | Armin Braun | 10 June 2019, 10:50:37 UTC | Better Exception in NetworkUtilsTests (#42109) * We are still running into an exception here every so often * Adjusted exception to contain interface name * Relates to #41549 | 28 January 2020, 21:23:38 UTC |
| 0c03754 | Jason Tedor | 02 May 2019, 20:35:55 UTC | Simplify filtering addresses on interfaces (#41758) This commit is a refactoring of how we filter addresses on interfaces. In particular, we refactor all of these methods into a common private method. We also change the order of logic to first check if an address matches our filter and then check if the interface is up. This is to possibly avoid problems we are seeing where devices are flapping up and down while we are checking for loopback addresses. We do not expect the loopback device to flap up and down so by reversing the logic here we avoid that problem on CI machines. Finally, we expand the error message when this does occur so that we know which device is flapping. | 28 January 2020, 21:16:23 UTC |
| 8a28c8d | Christoph Büscher | 28 January 2020, 14:44:13 UTC | Fix sporadic failures in QueryStringQueryTests#testToQueryFuzzyQueryAutoFuziness (#43322) (#51531) This commit ensures that the test does not use reserved keyword (OR, AND, NOT) when generating the random query strings. Backport of #43322 Co-authored-by: Jim Ferenczi <jim.ferenczi@elastic.co> | 28 January 2020, 14:44:13 UTC |
| f86c1bc | Jason Tedor | 28 January 2020, 10:42:11 UTC | Upgrade the bundled JDK to JDK 13.0.2 (#51511) This commit upgrades the JDK bundled in the Docker images to JDK 13.0.2, the latest available patch release of the JDK. | 28 January 2020, 10:51:05 UTC |
| aab6cae | Mark Vieira | 24 January 2020, 20:47:24 UTC | Delete failing JJBB experimental job | 24 January 2020, 20:47:36 UTC |
| 853e33a | Armin Braun | 24 January 2020, 15:34:13 UTC | Retry GCS Resumable Upload on Error 410 (#45963) (#51419) A resumable upload session can fail on with a 410 error and should be retried in that case. I added retrying twice using resetting of the given `InputStream` as the retry mechanism since the same approach is used by the AWS S3 SDK already as well and relied upon by the S3 repository implementation. Related GCS documentation: https://cloud.google.com/storage/docs/json_api/v1/status-codes#410_Gone | 24 January 2020, 15:34:13 UTC |
| a388cf7 | Nhat Nguyen | 23 January 2020, 21:32:03 UTC | Account soft-deletes in FrozenEngine (#51362) Currently, we do not exclude soft-deleted documents when opening index reader in the FrozenEngine. Relates #50775 Backport of #51192 | 23 January 2020, 21:32:03 UTC |
| 4a5cdf5 | Zachary Tong | 23 January 2020, 16:12:24 UTC | Mute ResultSetTestCase#testGettingDateWithoutCalendar Seems flaky with java13 on JdbcResultSetIT, fails reliably. Tracking issue: https://github.com/elastic/elasticsearch/issues/50035 | 23 January 2020, 16:12:24 UTC |
| d871dfd | Henning Andersen | 23 January 2020, 10:25:19 UTC | Revert "Workaround for JDK 14 EA FileChannel.map issue (#50523)" (#51323) This reverts commit c7fd24ca1569a809b499caf34077599e463bb8d6. Now that JDK-8236582 is fixed in JDK 14 EA, we can revert the workaround. Relates #50523 and #50512 | 23 January 2020, 11:03:27 UTC |
| 7bebc65 | Henning Andersen | 10 January 2020, 12:54:32 UTC | GlobalBuildInfo support packed-refs with work-tree (#50791) The packed-refs support was using the original .git path, changed to use the real .git directory after reference from worktree has been followed. Relates #47464 | 23 January 2020, 10:59:03 UTC |
| be72e3f | Martijn van Groningen | 21 January 2020, 14:37:38 UTC | Protects against NPE: 2> REPRODUCE WITH: ./gradlew ':x-pack:plugin:watcher:test' --tests "org.elasticsearch.xpack.watcher.history.HistoryTemplateTransformMappingsTests.testTransformFields" -Dtests.seed=26754396AB9C1A30 -Dtests.security.manager=true -Dtests.locale=lv-LV -Dtests.timezone=America/Dominica -Dcompiler.java=13 -Druntime.java=8 2> java.lang.NullPointerException at __randomizedtesting.SeedInfo.seed([26754396AB9C1A30:B2A3CA27E260803B]:0) at org.elasticsearch.xpack.watcher.history.HistoryTemplateTransformMappingsTests.lambda$testTransformFields$1(HistoryTemplateTransformMappingsTests.java:85) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193) at java.util.HashMap$ValueSpliterator.forEachRemaining(HashMap.java:1628) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472) at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499) at org.elasticsearch.xpack.watcher.history.HistoryTemplateTransformMappingsTests.lambda$testTransformFields$2(HistoryTemplateTransformMappingsTests.java:88) at org.elasticsearch.test.ESTestCase.assertBusy(ESTestCase.java:892) at org.elasticsearch.test.ESTestCase.assertBusy(ESTestCase.java:877) at org.elasticsearch.xpack.watcher.history.HistoryTemplateTransformMappingsTests.testTransformFields(HistoryTemplateTransformMappingsTests.java:74) | 23 January 2020, 08:43:22 UTC |
| 49ae3be | Mark Vieira | 22 January 2020, 21:50:48 UTC | Add openjdk 15 to Java matrix testing rotation (#51335) | 22 January 2020, 21:57:25 UTC |
| 2db220c | Mark Vieira | 21 January 2020, 23:16:29 UTC | Whitelist a few more matrix parameter characters Signed-off-by: Mark Vieira <portugee@gmail.com> | 21 January 2020, 23:17:41 UTC |
| 9a6324f | Martijn van Groningen | 21 January 2020, 12:48:39 UTC | Muting of this test was forgotten in 6.8 branch. Relates #48381 | 21 January 2020, 12:48:39 UTC |
| 93d7552 | Darren Foong | 13 January 2020, 16:11:52 UTC | Improve warning value extraction performance in Response (#50208) This commit improves the performance of warning value extraction in the low-level REST client, and is similar to the approach taken in be connected to Elasticsearch through a proxy that injects its own warnings. | 15 January 2020, 00:01:13 UTC |
| 2acb910 | Mark Vieira | 14 January 2020, 17:53:46 UTC | Add matrix job params as build scan tag Signed-off-by: Mark Vieira <portugee@gmail.com> | 14 January 2020, 17:54:48 UTC |
| ef417ee | Nhat Nguyen | 14 January 2020, 03:34:37 UTC | Remove outdated requirement of CCR (#50859) (#50948) With retention leases, users do not need to set index.soft_deletes.retention.operations. This change removes it from the requirements of CCR. Backport of #50859 | 14 January 2020, 03:34:37 UTC |
| 4eebbce | Mark Vieira | 13 January 2020, 17:31:39 UTC | Fix build scan logic to support folder nested Jenkins job names Signed-off-by: Mark Vieira <portugee@gmail.com> | 13 January 2020, 17:32:44 UTC |
| 624ebb5 | junmuz | 13 January 2020, 14:47:36 UTC | [DOCS] Correct typo in `ignore_malformed` mapping parm docs (#50780) | 13 January 2020, 14:50:23 UTC |
| 9d7226c | Mark Vieira | 10 January 2020, 23:01:06 UTC | Improve build scan tags and values for Jenkins matrix jobs (#50881) | 10 January 2020, 23:01:18 UTC |
| a13aeae | James Rodewig | 10 January 2020, 17:24:42 UTC | [DOCS] Remove unneeded parentheses from range query snippet 49fd152be2abb0730bd5b8a80082c3ca83531115 (6.8 backport of #50830) unintentionally added an unneeded parentheses to the `time_zone` snippet of the range query docs. This removes that parentheses. | 10 January 2020, 17:25:08 UTC |
| 49fd152 | James Rodewig | 10 January 2020, 13:23:25 UTC | [DOCS] Fix time_zone example in range query docs (#50830) One of the example snippets in the range query docs was missing a required 'T' in the `date` format. This adds the required 'T'. | 10 January 2020, 13:26:43 UTC |
| 28f2578 | Martijn van Groningen | 09 January 2020, 08:01:55 UTC | Wrap triggering of a watch inside an assertBusy(...) invocation This test replaces the watch index after watcher got started. This triggers watches being reloaded and while this happens the trigger engine is paused, which disallows watches from being triggered. At this time there are no watches in the .watches index and I think this is just unlucky timing. Reloading of watches happens in the background and the watch state can be started when that happens. For normal schedule trigger engines this is not an issue, because watches that are meant to be triggered are triggered when the engine triggers the next time. However for the mock scheduled trigger engine this is different, because watches are triggered programatically and there is no retry in this test. I think just adding `timeWarp().trigger("mywatch");` inside a `assertBusy(...)`` is the right fix here. If it fails because the mock schedule trigger engine is paused then the test will try again. In the mean time the the watches can be reloaded, which then resumes the mock scheduled trigger engine. Closes #50658 | 09 January 2020, 08:06:45 UTC |
| 8349bd4 | Ioannis Kakavas | 09 January 2020, 07:41:04 UTC | Mute SamlAuthenticatorTests in Azulu Zulu (#50779) See #49742 | 09 January 2020, 07:52:46 UTC |
| d92d7b6 | Valentin Crettaz | 08 January 2020, 16:50:03 UTC | [DOCS] Fixed typos (_op => op) in Painless context docs (#50301) | 08 January 2020, 16:55:59 UTC |
| deaea97 | Nhat Nguyen | 07 January 2020, 15:08:13 UTC | Disable auto refresh in testSegmentsStats (#50689) If an auto-refresh happens, then version_map_memory is reset to 0. By default, the auto-refresh occurs for every second in the first 30 seconds until search becomes idle. Closes #50362 | 07 January 2020, 23:16:13 UTC |
| 4482f73 | Mayya Sharipova | 07 January 2020, 17:20:09 UTC | Fix NPE bug inner_hits (#50709) When there several subqueries on different relations of the join field, and only one of subqueries is using inner_hits, NPE occurs. This PR prevents NPE error. Closes #50539 | 07 January 2020, 19:51:59 UTC |
| 338a538 | James Rodewig | 07 January 2020, 15:17:54 UTC | [DOCS] Update SQL REST API pages for new structure (#50690) This updates up a reference that assumes a single page in the "Paginating through a large response" section. It also reformats a tip for the Kibana console. Closes #50688 | 07 January 2020, 15:35:30 UTC |
| 1365ef0 | Henning Andersen | 06 January 2020, 11:18:12 UTC | Workaround for JDK 14 EA FileChannel.map issue (#50523) FileChannel.map provokes static initialization of ExtendedMapMode in JDK14 EA, which needs elevated privileges. Relates #50512 | 06 January 2020, 11:23:49 UTC |
| a257ae7 | Jake | 30 December 2019, 20:38:59 UTC | [DOCS] Bump copyright to 2019 for Java HLRC license (#50206) | 30 December 2019, 20:40:41 UTC |
| b1e0627 | riverbuilding | 30 December 2019, 13:48:10 UTC | [DOCS] Correct Painless operator typos (#50472) | 30 December 2019, 13:51:10 UTC |
| fcb62f2 | James Rodewig | 23 December 2019, 18:11:31 UTC | [DOCS] Percentile aggs are non-deterministic (#50468) Percentile aggregations are non-deterministic. A percentile aggregation can produce different results even when using the same data. Based on [this discuss post][0], the non-deterministic property stems from processes in Lucene that can affect the order in which docs are provided to the aggregation. This adds a warning stating that the aggregation is non-deterministic and what that means. [0]: https://discuss.elastic.co/t/different-results-for-same-query/111757 | 23 December 2019, 18:17:25 UTC |
| 6e60476 | Mark Vieira | 20 December 2019, 23:52:24 UTC | Update BWC CI versions for 6.8.6 release | 20 December 2019, 23:52:24 UTC |
| 469c234 | Lisa Cawley | 20 December 2019, 21:34:23 UTC | [6.8][DOCS] Updates Stack Overview links (#50447) | 20 December 2019, 21:34:23 UTC |
| 9548dfc | Nhat Nguyen | 20 December 2019, 16:47:47 UTC | Close engine before reset log appender (#50390) Merge threads can run and access the mock appender after we have stopped it. Closes #50315 | 20 December 2019, 19:57:01 UTC |
| a2b7532 | Marios Trivyzas | 19 December 2019, 22:19:22 UTC | SQL: Fix issue with CAST and NULL checking. (#50371) Previously, during expression optimisation, CAST would be considered nullable if the casted expression resulted to a NULL literal, and would be always non-nullable otherwise. As a result if CASE was wrapped by a null check function like IS NULL or IS NOT NULL it was simplified to TRUE/FALSE, eliminating the actual casting operation. So in case of an expression with an erroneous casting like CAST('foo' AS DATETIME) IS NULL it would be simplified to FALSE instead of throwing an Exception signifying the attempt to cast 'foo' to a DATETIME type. CAST now always returns Nullability.UKNOWN except from the case that its result evaluated to a constant NULL, where it returns Nullability.TRUE. This way the IS NULL/IS NOT NULL don't get simplified to FALSE/TRUE and the CAST actually gets evaluated resulting to a thrown Exception. Fixes: #50191 (cherry picked from commit 671e07a931cd828661e226cba22a5d38804a17a5) | 20 December 2019, 09:46:36 UTC |
| 880a36d | Mark Vieira | 19 December 2019, 22:37:25 UTC | Disable experimental job trigger Signed-off-by: Mark Vieira <portugee@gmail.com> | 19 December 2019, 22:42:37 UTC |
| dc6b25a | Mark Vieira | 19 December 2019, 20:55:11 UTC | Add shell script for performing atomic pushes across branches (#50401) | 19 December 2019, 20:56:16 UTC |
| 4098d00 | lcawl | 18 December 2019, 19:46:00 UTC | [DOCS] Fixes security links | 18 December 2019, 19:48:09 UTC |
| f849d92 | Ryan Ernst | 18 December 2019, 19:28:52 UTC | Add release notes for 6.8.6 | 18 December 2019, 19:29:45 UTC |
| 1b2a59a | Ryan Ernst | 18 December 2019, 17:32:58 UTC | Bump maintenance version to 6.8.7 | 18 December 2019, 17:38:03 UTC |
| b1c3ee2 | James Rodewig | 18 December 2019, 14:14:48 UTC | [DOCS] Add placeholder for 6.8.6 release notes (#50314) | 18 December 2019, 14:14:48 UTC |
| 3d9f765 | James Rodewig | 12 December 2019, 13:38:48 UTC | [DOCS] Correct percentile rank agg example response (#50052) The example snippets in the percentile rank agg docs use a test dataset named `latency`, which is generated from docs/gradle.build. At some point the dataset and example snippets were updated, but the text surrounding the snippets was not. This means the text and the example snippets shown no longer match up. This corrects that by changing the snippets using /TESTRESPONSE magic comments. | 12 December 2019, 14:16:15 UTC |
| 8744367 | Nik Everett | 11 December 2019, 20:50:58 UTC | Docs: Remove broken [float] (#50098) This removes a broken [float] tag. In our docbook-based docs build it is just ignored silently. `--direct_html`, which I'm trying to move all of the books to ignores it but log a warning which fails the build. I *could* make it not log the warning, but this error is fairly rare and I feel like it is worth cleaning up. | 11 December 2019, 20:59:33 UTC |
| 8ec1447 | Henning Andersen | 11 December 2019, 16:18:51 UTC | Log attachment generation failures (#50080) Watcher logs when actions fail in ActionWrapper, but failures to generate an email attachment are not logged and we thus only know the type of the exception and not where/how it occurred. | 11 December 2019, 16:30:53 UTC |
| 5157076 | Yannick Welsch | 11 December 2019, 15:35:52 UTC | Fix delete- and update-by-query on indices without sequence numbers (#50077) This fixes a bug where delete-by-query and update-by-query were not working on an older index that did not have sequence numbers yet. The reason is that in a mixed-version 6.x/5.x cluster, documents can have a primary term but miss a sequence number. | 11 December 2019, 15:35:52 UTC |
| a2697dc | James Rodewig | 10 December 2019, 14:30:04 UTC | [DOCS] Remove shadow replica reference (#50029) Removes a reference to shadow replicas from the cat shards API docs and a comment in cluster/routing/UnassignedInfo.java. Shadow replicas were removed with #23906. | 10 December 2019, 14:33:07 UTC |
| 520a4e8 | James Rodewig | 18 September 2019, 13:44:28 UTC | [DOCS] Remove leveloffset for CCR docs (#46818) | 10 December 2019, 00:33:23 UTC |
| 50d5d84 | debadair | 09 December 2019, 23:22:11 UTC | [DOCS] Added older release notice. (#49996) | 09 December 2019, 23:22:11 UTC |
| 0fb4f04 | James Rodewig | 09 December 2019, 16:04:20 UTC | [DOCS] Correct `for in` example in Painless docs (#49991) Adds a needed `def` keyword to the `for in` example in the Painless docs. | 09 December 2019, 16:30:44 UTC |
| de8261f | Lisa Cawley | 06 December 2019, 23:55:17 UTC | [6.8][DOCS] Add CCR docs to the Elasticsearch Reference Guide (#45704) (#49952) | 06 December 2019, 23:55:17 UTC |
| 9a1bde2 | James Baiera | 05 December 2019, 18:53:51 UTC | Support es7 node http publish_address format (#49279) (#49843) Add parsing support to node http publish_address format cname/ip:port. | 05 December 2019, 18:53:51 UTC |
| 9bf6072 | István Zoltán Szabó | 05 December 2019, 09:14:52 UTC | [6.8][DOCS] Fixes typo in the ML anomaly detection time functions docs. (#49849) | 05 December 2019, 09:14:52 UTC |
| 62e2a03 | James Rodewig | 04 December 2019, 17:44:13 UTC | [DOCS] Document `minimum_should_match` defaults for `bool` query (#48865) Adds documentation for the `minimum_should_match` parameter to the `bool` query docs. Includes docs for the default values: - `1` if the `bool` query includes at least one `should` clause and no `must` or `filter` clauses - `0` otherwise | 04 December 2019, 17:52:43 UTC |
| 0a7fd8f | Yannick Welsch | 04 December 2019, 12:49:43 UTC | Add SecureSM support for newer IDEA versions (#49747) IntelliJ IDEA moved their JUnit runner to a different package. While this does not break running tests in IDEA, it leads to an ugly exception being thrown at the end of the tests: Exception in thread "main" java.lang.SecurityException: java.lang.System#exit(0) calls are not allowed at org.elasticsearch.secure_sm.SecureSM$2.run(SecureSM.java:248) at org.elasticsearch.secure_sm.SecureSM$2.run(SecureSM.java:215) at java.base/java.security.AccessController.doPrivileged(AccessController.java:310) at org.elasticsearch.secure_sm.SecureSM.innerCheckExit(SecureSM.java:215) at org.elasticsearch.secure_sm.SecureSM.checkExit(SecureSM.java:206) at java.base/java.lang.Runtime.exit(Runtime.java:111) at java.base/java.lang.System.exit(System.java:1781) at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:59) This commit adds support for newer IDEA versions in SecureSM. | 04 December 2019, 12:51:30 UTC |
| 1dab262 | Lisa Cawley | 30 November 2019, 01:16:38 UTC | [DOCS] Fixes usage of xpack-ref attribute (#49735) | 30 November 2019, 01:16:38 UTC |
