https://github.com/elastic/elasticsearch

sort by:
Revision Author Date Message Commit Date
7a013de Add cluster restart for security on basic (#42414) This performs a simple restart test to move a basic licensed cluster from no security (the default) to security & transport TLS enabled. Backport of: #41933 23 May 2019, 03:07:20 UTC
80a7e88 Ensure testAckedIndexing uses disruption index settings AbstractDisruptionTestCase set a lower global checkpoint sync interval setting, but this was ignored by testAckedIndexing, which has led to spurious test failures Relates #41068, #38931 22 May 2019, 17:13:54 UTC
41b31d0 Fix grammar problem in stemming reference. (#42148) 22 May 2019, 16:56:10 UTC
6def96a Fix a rendering issue in the geo envelope docs. (#42332) Previously the formatting information didn't display in the docs, and the sentence just rendered as "bounding rectangle in the format :". 22 May 2019, 16:56:08 UTC
0a78553 Fix testAutoFollowManyIndices On a slow CI worker, the test was failing an assertion. Closes #41234 22 May 2019, 15:33:52 UTC
6630d33 Rework discovery-ec2 docs (#41630) This commit reworks and clarifies the docs for the `discovery-ec2` plugin: - folds the tiny "Getting started with AWS" into the page on configuration - spells out the name of each setting in full instead of noting the `discovery.ec2` prefix at the top of the page. - replaces each `(Secure)` marker with a sentence describing what that means in situ - notes some missing defaults - clarifies the behaviour of `discovery.ec2.groups` (dependent on `.any_group`) - clarifies what `discovery.ec2.host_type` is for - adds `discovery.ec2.tag.TAGNAME` as a (meta-)setting rather than describing it in a separate section - notes that the tags mentioned in `discovery.ec2.tag.TAGNAME` cannot contain colons (see #38406) - clarifies the EC2-specific interface names and what they're for - reorders and rewords the recommendations for storage - expands on why you should not span a cluster across regions - adds a suggestion on protecting instances against termination during scale-in - reformat to 80 columns where possible Fixes #38406 22 May 2019, 08:51:39 UTC
deecdec Fix off-by-one error in an index shard test There is an off-by-one error in this test. It leads to the recovery thread never being started, and that means joining on it will wait indefinitely. This commit addresses that by fixing the off-by-one error. Relates #42325 21 May 2019, 23:20:58 UTC
de2180c Execute actions under permit in primary mode only (#42241) Today when executing an action on a primary shard under permit, we do not enforce that the shard is in primary mode before executing the action. This commit addresses this by wrapping actions to be executed under permit in a check that the shard is in primary mode before executing the action. 21 May 2019, 20:24:21 UTC
1428a43 Avoid unnecessary persistence of retention leases (#42299) Today we are persisting the retention leases at least every thirty seconds by a scheduled background sync. This sync causes an fsync to disk and when there are a large number of shards allocated to slow disks, these fsyncs can pile up and can severely impact the system. This commit addresses this by only persisting and fsyncing the retention leases if they have changed since the last time that we persisted and fsynced the retention leases. 21 May 2019, 18:01:45 UTC
802e00a Remove 7.0.2 (#42282) 7.0.2 removed, since it will never be, fixing branch consistency check. 21 May 2019, 13:51:55 UTC
d1b473e Move the FIPS configuration back to the build plugin (#41989) * Move the FIPS configuration back to the build plugin This is necesary for external users of build-tools. Closes #41721 21 May 2019, 13:41:26 UTC
6f32bfa Remove stray back tick that's messing up table format (#41705) 21 May 2019, 13:00:23 UTC
510850d Add missing comma in code section (#41678) Missing comma in code section (line 114) is added to the doc file. 21 May 2019, 12:53:06 UTC
217e2fb Use spearate testkit dir for each run (#42013) Gradle Testkit reuses the teskit dir by default between tests. With this change we use a temporary one for each run hoping it will fix #41431 21 May 2019, 11:02:14 UTC
12ba9f0 version bump 7.1.0 -> 7.1.1 (includes 6.8.1 version) (#42242) 20 May 2019, 21:19:06 UTC
2f676d0 Remove deprecated _source_exclude and _source_include from get API spec (#42188) Support for these parameters was removed in #35097. The spec were left outdated. 20 May 2019, 21:09:51 UTC
cdad4ae fix assumption that 6.7 is last 6.x release (#42255) 20 May 2019, 19:32:44 UTC
4dbf593 7.1.0 release notes initial commit (#42208) 20 May 2019, 16:00:00 UTC
c4df03d [DOCS] Updates TLS configuration info (#41983) 20 May 2019, 13:22:19 UTC
43a8648 [DOCS] Updates docs release status for 7.1.0 (#42023) 20 May 2019, 13:07:50 UTC
c55978c Clarify rolling upgrade fallback to restart upgrade (#42161) Adds a note that restarting half-or-more of the master-eligible nodes means you're no longer doing a rolling upgrade, and may need to upgrade all the things before the cluster returns to health. 16 May 2019, 17:42:21 UTC
606a173 Don't verify evictions in testFilterCacheStats (#42091) If a background merge and refresh happens after a search but before a stats query, then evictions will be non-zero. Closes #32506 15 May 2019, 23:04:05 UTC
66d555b Adjust load and timeout in testShrinkIndexPrimaryTerm (#42098) This test can create and shuffle 2*(3*5*7) = 210 shards which is quite heavy for our CI. This commit reduces the load, so we don't timeout on CI. Closes #28153 15 May 2019, 23:03:57 UTC
08d38da SQL: Fix issue regarding INTERVAL * number (#42014) Interval * integer number is a valid operation which previously was only supported for foldables (literals) and not when a field was involved. That was because: 1. There was no common type returned for that combination 2. The `BinaryArithmeticOperation` was permitting the multiplication (called by fold()) but the BinaryArithmeticProcessor didn't allow it Moreover the error message for invalid arithmetic operations was wrong because of the issue with the overloading methods of `LoggerMessageFormat.format`. Fixes: #41239 Fixes: #41200 (cherry picked from commit 91039bab12d3ef27d6eac9cdc891a3b3ad0c694d) 15 May 2019, 20:46:53 UTC
5071d43 Enforce transport TLS on Basic with Security (#42150) If a basic license enables security, then we should also enforce TLS on the transport interface. This was already the case for Standard/Gold/Platinum licenses. For Basic, security defaults to disabled, so some of the process around checking whether security is actuallY enabled is more complex now that we need to account for basic licenses. 15 May 2019, 18:04:43 UTC
7bd161d Mute IndexStatsIT#testFilterCacheStats See https://github.com/elastic/elasticsearch/issues/32506 15 May 2019, 14:22:23 UTC
14020c5 Minor cluster coordination docs fixes (#42111) Fixes a typo and a badly-formatted warning. 15 May 2019, 13:28:13 UTC
eb8f171 Log cluster UUID when committed (#42065) Today we do not expose the cluster UUID in any logs by default, but it would be useful to see it. For instance if a user starts multiple nodes as separate clusters then they will silently remain as separate clusters even if they are subsequently reconfigured to look like a single cluster. This change logs the committed cluster UUID the first time the node encounters it. 14 May 2019, 09:36:10 UTC
07adb3a [DOCS] Add `:` to render multiple inline macros in Asciidoctor (#41615) 13 May 2019, 12:51:57 UTC
07d3570 [DOCS] Rewrite 'rewrite' parameter docs (#42018) 13 May 2019, 12:43:57 UTC
8266422 Increase the sample space for random inner hits name generator (#42057) (#42073) This commits changes the minimum length for inner hits name to avoid name collision which sometimes failed the test. 12 May 2019, 00:32:45 UTC
3b346ad Remove reference to fs.data.spins in docs We long ago removed fs.data.spins from the nodes stats. This commit removes reference to this in the docs. 10 May 2019, 15:49:24 UTC
d366b80 Remove extra `ms` from log message (#42068) This log message logs a `TimeValue` which includes units, but also logs an extra `ms`. This commit removes the extra `ms`. 10 May 2019, 13:04:09 UTC
478f65c Disable rhel8 in packaging tests (#41924) This commit disables rhel 8 from being tested in vagrant packaging tests. The vagrant image we use is beta release, but RHEL 8 was just released, which has caused the package mirrors for the beta to stop working. 10 May 2019, 06:43:10 UTC
6c24dc0 [DOCS] Adds placeholder for 7.1.0 release notes (#42024) 09 May 2019, 17:10:19 UTC
16e3ea3 [ML] relax set upgrade mode test to match what is guaranteed (#41958) (#41977) * [ML] relax set upgrade mode test to match what is guaranteed * removing unused import 09 May 2019, 16:10:14 UTC
5536104 [DOCS] Updates security configuration overview (#41982) 09 May 2019, 15:23:58 UTC
cfa7f8f Fix IAE on cross_fields query introduced in 7.0.1 (#41938) If the max doc in the index is greater than the minimum total term frequency among the requested fields we need to adjust max doc to be equal to the min ttf. This was removed by mistake when fixing #41125. Closes #41934 09 May 2019, 14:11:58 UTC
6a177db [DOCS] Replace table with def list for ids query (#41865) 09 May 2019, 13:53:13 UTC
0c0f1aa Fix wrong property name (#40636) 09 May 2019, 06:53:48 UTC
98be9d2 Add note about ILM action ordering (#41771) Adds a note clarifying that actions are ordered automatically. 08 May 2019, 22:42:39 UTC
fc132d4 Add corretto 11 and 8 to runtime javas (#41946) We now have coretto on the ephemeral CI images so we can add it to our regular java test matrix. On backporting will also add corretto8 to branches that support it. 08 May 2019, 13:38:31 UTC
a4dad72 Remove mention of bulk threadpool in examples (#41935) The `bulk` threadpool is now called `write`, but `bulk` is still used in some examples. This commit fixes that. Also, the only way `threadpool.bulk.write: 30` is a valid increase in the size of this threadpool is if you have 29 processors, which is an odd number of processors to have. This commit removes the "more threads" bit. 08 May 2019, 11:15:16 UTC
07275ef Node names in bootstrap config have no ports (#41569) In cases where node names and transport addresses can be muddled, it is unclear that `cluster.initial_master_nodes: master-a:9300` means to look for a node called `master-a:9300` rather than a node called `master-a` with transport port `9300`. This commit adds docs to that effect. 08 May 2019, 10:25:03 UTC
6b4e85b Allow reindexing into write alias (#41677) Fixes an issue where reindex currently fails if the destination is an alias pointing to multiple indices, even it is using a write index. Closes #41667 08 May 2019, 08:53:52 UTC
e244c1d Highlight the use of single-node discovery in docker docs (#41241) Relates to https://discuss.elastic.co/t/es-7-and-docker-single-node-cluster/176585 08 May 2019, 08:53:26 UTC
41cd810 Clarify settings in default SSL/TLS (#41931) The settings listed under the "Default values for TLS/SSL settings" heading are not actual settings, rather they are common suffixes that are used for settings that exist in a variety of contexts. This commit changes the way they are presented to reduce this confusion. Backport of: #41779 08 May 2019, 06:24:20 UTC
04116c9 SQL: Remove CircuitBreaker from parser (#41835) The CircuitBreaker was introduced as means of preventing a `StackOverflowException` during the build of the AST by the parser. The ANTLR4 grammar causes a weird behaviour for a Parser Listener. The `enterEveryRule()` method is often called with a different parsing context than the respective `exitEveryRule()`. This makes it difficult to keep track of the tree's depth, and a custom Map was used as an attempt of matching the contextes as they are encounter during `enter` and during `exit` of the rules. This approach had 2 important drawbacks: 1. It's hard to maintain this custom Map as the grammar changes. 2. The CircuitBreaker could often lead to false positives which caused valid queries to return an Exception and prevent them from executing. So, this removes completely the CircuitBreaker which is replaced be a simple handling of the `StackOverflowException` Fixes: #41471 (cherry picked from commit 1559a8e2dbd729138b52e89b7e80264c9f4ad1e7) 07 May 2019, 20:45:01 UTC
a22120d Handle serialization exceptions during publication (#41781) Today if an exception is thrown when serializing a cluster state during publication then the master enters a poisoned state where it cannot publish any more cluster states, but nor does it stand down as master, yielding repeated exceptions of the following form: ``` failed to commit cluster state version [12345] org.elasticsearch.cluster.coordination.FailedToCommitClusterStateException: publishing failed at org.elasticsearch.cluster.coordination.Coordinator.publish(Coordinator.java:1045) ~[elasticsearch-7.0.0.jar:7.0.0] at org.elasticsearch.cluster.service.MasterService.publish(MasterService.java:252) [elasticsearch-7.0.0.jar:7.0.0] at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService.java:238) [elasticsearch-7.0.0.jar:7.0.0] at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService.java:142) [elasticsearch-7.0.0.jar:7.0.0] at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher.java:150) [elasticsearch-7.0.0.jar:7.0.0] at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher.java:188) [elasticsearch-7.0.0.jar:7.0.0] at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:681) [elasticsearch-7.0.0.jar:7.0.0] at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor.java:252) [elasticsearch-7.0.0.jar:7.0.0] at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:215) [elasticsearch-7.0.0.jar:7.0.0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_144] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_144] at java.lang.Thread.run(Thread.java:748) [?:1.8.0_144] Caused by: org.elasticsearch.cluster.coordination.CoordinationStateRejectedException: cannot start publishing next value before accepting previous one at org.elasticsearch.cluster.coordination.CoordinationState.handleClientValue(CoordinationState.java:280) ~[elasticsearch-7.0.0.jar:7.0.0] at org.elasticsearch.cluster.coordination.Coordinator.publish(Coordinator.java:1030) ~[elasticsearch-7.0.0.jar:7.0.0] ... 11 more ``` This is because it already created the publication request using `CoordinationState#handleClientValue()` but then it fails before accepting it. This commit addresses this by performing the serialization before calling `handleClientValue()`. Relates #41090, which was the source of such a serialization exception. 07 May 2019, 17:00:03 UTC
491c0cd Fix fractional seconds for strict_date_optional_time (#41871) The fractional seconds portion of strict_date_optional_time was accidentally copied from the printer, which always prints at least 3 fractional digits. This commit fixes the formatter to allow 1 or 2 fractional seconds. closes #41633 07 May 2019, 16:10:25 UTC
1e9e088 [DOCS] Rewrite `exists` query docs (#41868) 07 May 2019, 13:23:42 UTC
f9ce3f7 [DOCS] Fix typo referring to multi search API 07 May 2019, 13:09:11 UTC
c1c8af5 Provide names for all artifact repositories (#41857) This commit adds a name for each Maven and Ivy repository used in the build. 07 May 2019, 10:35:54 UTC
ac866a3 Remove dropped Docker task dependencies Some Docker tasks were removed in a previous commit yet they were still depended on here. This commit removes references to these dropped Docker tasks. 07 May 2019, 01:38:59 UTC
3c7a75c Add tasks to build Docker build context artifacts (#41819) This commit adds some tasks to generate dedicated Docker build context artifacts. 07 May 2019, 01:05:57 UTC
ece62c6 Log warning when unlicensed realms are skipped (#41832) Because realms are configured at node startup, but license levels can change dynamically, it is possible to have a running node that has a particular realm type configured, but that realm is not permitted under the current license. In this case the realm is silently ignored during authentication. This commit adds a warning in the elasticsearch logs if authentication fails, and there are realms that have been skipped due to licensing. This message is not intended to imply that the realms could (or would) have successfully authenticated the user, but they may help reduce confusion about why authentication failed if the caller was expecting the authentication to be handled by a particular realm that is in fact unlicensed. Backport of: #41778 06 May 2019, 23:58:16 UTC
13e9d4d Clarify that path_match also considers object fields. (#41658) The `path_match` and `path_unmatch` parameters in dynamic templates match on object fields in addition to leaf fields. This is not obvious and can cause surprising errors when a template is meant for a leaf field, but there are object fields that match. This PR adds a note to the docs to describe the current behavior. 06 May 2019, 21:53:30 UTC
3965730 Clarify _doc is a permanent part of certain document APIs. (#41727) We received some feedback that it is not completely clear why `_doc` is present in the typeless document APIs: > The new index APIs are PUT {index}/_doc/{id} in case of explicit ids and POST {index}/_doc for auto-generated ids."_ Isn't this contradicting? Specifying *types in requests is deprecated*, but we are supposed to still mention *_doc* in write requests? This PR updates the 'removal of types' documentation to try to clarify that `_doc` now represents the endpoint name, as opposed to a type. 06 May 2019, 17:50:41 UTC
2161323 Remove the jdk directory to save space on bwc tests (#41743) * Revert "Revert "Clean up clusters between tests (#41187)"" This reverts commit 9efc853aa668e285ede733d37b6fc7a0f4b02041. * Remove the jdk directory to save space on bwc tests This PR adresses the same concern as #41187 in a different way. It removes only the JDK from the distribution once the cluster stops, so we keep the same disk space requirements as before adding the JDK. This is still a temporary measure, testclusters already deals with this by doing the equivalent of `cp -l` instead of an actual copy. 06 May 2019, 17:03:24 UTC
2a46079 [DOCS] Rewrite `term` query docs for new format (#41498) * [DOCS] Restructure `term` query docs. 06 May 2019, 15:26:46 UTC
fc0012e Mute PermissionsIT#testWhen[...]ByILMPolicy (#41860) Relates #41440 Relates #41858 06 May 2019, 14:17:42 UTC
b9ab5bf Update security acknowledgement messages for basic (#41826) When applying a license update, we provide "acknowledgement messages" that indicate which features will be affected by the change in license. This commit updates the messages that are provided when installing a basic license, so that they reflect the changes made to the security features that are included in that license type. Backport of: #41776 06 May 2019, 06:40:54 UTC
c2923c1 Set metadata sources for Ivy repositories (#41818) We have faked some Ivy repositories on a few artifact locations. Today when Gradle attempts to resolve these artifacts, it follows its default strategy to search for Gradle metadata, then Maven POM files, then Ivy descriptors, and finally will fallback to looking directly for the artifact. This wastes times on remote network calls that will 404 anyway since these metadata resources will not exist for these fake Ivy repositories. This commit overrides the Gradle strategy to look directly for artifacts. 05 May 2019, 15:17:00 UTC
2d0bd1e Enforce that Maven/Ivy repositories use https (#41812) This commit adds a check when a repository is added that we are using https instead of http. 04 May 2019, 16:49:31 UTC
a11b9a4 Use a proper repository for ml-cpp artifacts (#41817) This switches the strategy used to download machine learning artifacts from a manual download through S3 to using an Ivy repository on top of S3. This gives us all the benefits of Gradle dependency resolution including local caching. 04 May 2019, 16:45:08 UTC
c34f71c Update some more S3 artifact locations to use https This commit updates some additional S3 artifact locations to use https instead of http. Relates 8c017533f9484200cc1c669ea364790eb99d5787 04 May 2019, 12:30:45 UTC
8c01753 Use https for artifact locations This commit switches to using https for some artifact locations. 03 May 2019, 20:17:01 UTC
13d54f3 [DOCS] Adds placeholders for 7.1 highlights and breaking changes (#41773) 03 May 2019, 15:38:35 UTC
ca6fecd Recommend use of ln1p/log1p to avoid negative scores (#41610) As negative scores will now cause an error, and it is easy to accidentally produce negative scores with some of the built-in modifiers (especially `ln` and `log`), this adjusts the documentation to more strongly recommend the use of `ln1p` and `log1p` instead. Also corrects some awkward formatting on the note sections following the table. 03 May 2019, 15:10:21 UTC
75890bd Upgrade keystore on package install (#41755) When Elasticsearch is run from a package installation, the running process does not have permissions to write to the keystore. This is because of the root:root ownership of /etc/elasticsearch. This is why we create the keystore if it does not exist during package installation. If the keystore needs to be upgraded, that is currently done by the running Elasticsearch process. Yet, as just mentioned, the Elasticsearch process would not have permissions to do that during runtime. Instead, this needs to be done during package upgrade. This commit adds an upgrade command to the keystore CLI for this purpose, and that is invoked during package upgrade if the keystore already exists. This ensures that we are always on the latest keystore format before the Elasticsearch process is invoked, and therefore no upgrade would be needed then. While this bug has always existed, we have not heard of reports of it in practice. Yet, this bug becomes a lot more likely with a recent change to the format of the keystore to remove the distinction between file and string entries. 03 May 2019, 14:35:16 UTC
2790d52 Fix discovery config in docker-compose docs (#41753) Today's `docker-compose` docs are missing the `discovery.seed_nodes` config on one of the nodes. With today's configuration the cluster can still form the first time it is started, because `cluster.initial_master_nodes` requires both nodes to bootstrap the cluster which ensures that each discover the other. However if `es02` is elected master it will remove `es01` from the voting configuration and then when restarted it will form a cluster on its own without needing to do any discovery. Meanwhile `es01` doesn't know how to find `es02` after a restart so will be unable to join this cluster. This commit fixes this by adding the missing configuration. Relates #41394, which fixes a different `docker-compose.yml` in the same way. 03 May 2019, 08:48:26 UTC
dec7d6e Adds version 6.7.3 02 May 2019, 16:35:25 UTC
5795494 Mute RejectedExecutionTests#testHistoryAndTriggeredOnRejection 02 May 2019, 09:52:21 UTC
b7fe3c0 Use separate tasks per bwc artifact (#41728) This commit changes the bwc builds from a single task for a branch to a task for each bwc artifact. This reduces the bwc build time when only needing a specific artifact, for example when running cluster restart tests on a mac, the windows artifacts or rpm/debs are not needed. This also includes fixes for CollectionVersionTests needed for the 7.1 branch 02 May 2019, 03:11:10 UTC
cf0a1d1 Correct that 6.8 is the last branch in 6.x This commit adjusts for the fact that we have created a 6.8 branch as the last minor in the 6.x series. 02 May 2019, 00:01:49 UTC
5cd2d3a Run packaging tests on RHEL 8 (#41662) 01 May 2019, 23:21:45 UTC
eab994e Flip 7.1 docs to unreleased This version is not yet released so this commit flips the docs state to unreleased. 01 May 2019, 21:46:24 UTC
f64d690 Drop distinction in entries for keystore (#41701) Today we allow adding entries from a file or from a string, yet we internally maintain this distinction such that if you try to add a value from a file for a setting that expects a string or add a value from a string for a setting that expects a file, you will have a bad time. This causes a pain for operators such that for each setting they need to know this difference. Yet, we do not need to maintain this distinction internally as they are bytes after all. This commit removes that distinction and includes logic to upgrade legacy keystores. 01 May 2019, 20:22:34 UTC
49e8727 Fix minimum compatible version after 6.8 This commit fixes the minimum compatible version after the introduction of 6.8. 01 May 2019, 20:19:42 UTC
9970eb5 Add negative tests for security features in basic Assert that API Keys, Tokens, DLS/FLS do not work in basic 01 May 2019, 18:01:43 UTC
be6cfb4 Add test for security on basic license. This is modelled on the qa test for TLS on basic. It starts a cluster on basic with security & performs a number of security related checks. It also performs those same checks on a trial license. 01 May 2019, 18:01:40 UTC
978a3ac Security on Basic License This adds support for using security on a basic license. It includes: - AllowedRealmType.NATIVE realms (reserved, native, file) - Roles / RBAC - TLS (already supported) It does not support: - Audit - IP filters - Token Service & API Keys - Advanced realms (AD, LDAP, SAML, etc) - Advanced roles (DLS, FLS) - Pluggable security As with trial licences, security is disabled by default. This commit does not include any new automated tests, but existing tests have been updated. 01 May 2019, 18:01:36 UTC
18a728d Show SSL usage when security is not disabled (#40761) It is possible to have SSL enabled but security disabled if security was dynamically disabled by the license type (e.g. trial license). e.g. In the following configuration: xpack.license.self_generated.type: trial # xpack.security not set, default to disabled on trial xpack.security.transport.ssl.enabled: true The security feature will be reported as available: true enabled: false And in this case, SSL will be active even though security is not enabled. This commit causes the X-Pack feature usage to report the state of the "ssl" features unless security was explicitly disabled in the settings. Backport of: #40672 01 May 2019, 17:32:24 UTC
2a5d4ee Add 6.8 version constant This commit adds the 6.8 version constant to the 7.0 branch. 01 May 2019, 17:31:15 UTC
367b1f0 Bump 7.1 branch to version 7.1.0 This commit bumps the version on the 7.1 branch to 7.1.0. 01 May 2019, 17:31:14 UTC
5922803 Bump 7.0 branch version to 7.0.2 (#41714) 01 May 2019, 15:22:31 UTC
5b5e574 Add release notes for 7.0.1 release (#41644) This commit adds release notes for the 7.0.1 release. In addition, there is a minor change to the current file structure so that we now have a 7.0.asciidoc file instead of a 7.0.0.asciidoc file. This makes the release notes for 7.0 consistent with other versions. 01 May 2019, 14:34:08 UTC
8a054ae [DOCS] Doc version bump for 7.0.1 (#41706) 01 May 2019, 14:26:19 UTC
76c08a9 [DOCS] Reword `type` query deprecation note for Asciidoctor migration (#41595) 01 May 2019, 13:32:54 UTC
01f0b87 Fix Watcher deadlock that can cause in-abilty to index documents. (#41418) (#41685) This commit removes the usage of the `BulkProcessor` to write history documents and delete triggered watches on a `EsRejectedExecutionException`. Since the exception could be handled on the write thread, the write thread can be blocked waiting on watcher threads (due to a synchronous method). This is problematic since those watcher threads can be blocked waiting on write threads. This commit also moves the handling of the exception to the generic threadpool to avoid submitting write requests from the write thread pool. fixes #41390 30 April 2019, 21:12:51 UTC
858c854 [DOCS] Move block delimiter and anchor in 'Configuring Security' for Asciidoctor migration (#41604) 30 April 2019, 20:41:40 UTC
15033f7 [DOCS] Escape quotes to avoid smart quotes in Asciidoctor (#41603) 30 April 2019, 20:31:41 UTC
530c762 [DOCS] Remove soft line breaks (+) for Asciidoctor migration (#41600) 30 April 2019, 20:23:32 UTC
b4222d3 [DOCS] Move beta[] tag for Asciidoctor migration (#41599) 30 April 2019, 20:04:36 UTC
0119bac [DOCS] Escape commas in deprecated[] for Asciidoctor migration (#41598) 30 April 2019, 19:53:14 UTC
3c226f0 [DOCS] Escape depcreated[] note for Asciidoctor migration (#41608) 30 April 2019, 19:20:00 UTC
de47a3f [DOCS] Add attribute to escape minimal pt token link in Asciidoctor (#41613) 30 April 2019, 18:12:27 UTC
7c9e817 [DOCS] Allow attribute substitution in titleabbrevs for Asciidoctor migration (#41574) 30 April 2019, 17:51:20 UTC
2ce2ff6 [DOCS] Add anchors for Asciidoctor migration (#41648) 30 April 2019, 14:25:02 UTC
6c58a8b Fix TokenBackwardsCompatibilityIT unexpected type warn header Fixes a test failure (#41671) which is due to unexpected type warning headers when version 7.0.1 was released. 30 April 2019, 14:02:21 UTC
back to top