| 816e6f6 | Martijn van Groningen | 09 November 2018, 16:43:43 UTC | [CCR] Validate remote cluster license as part of put auto follow pattern api call (#35364) Validate remote cluster license as part of put auto follow pattern api call in addition of validation that when auto follow coordinator starts auto following indices in the leader cluster. Also added qa module that tests what happens to ccr after downgrading to basic license. Existing active follow indices should remain to follow, but the auto follow feature should not pickup new leader indices. | 09 November 2018, 16:44:51 UTC |
| 6045083 | Albert Zaharovits | 09 November 2018, 14:58:10 UTC | DOCS Add audit ignore settings to reference page (#35274) Adds the logfile audit ignore policy settings synopsis to the Auditing Reference page. | 09 November 2018, 16:07:12 UTC |
| f990a50 | Martijn van Groningen | 09 November 2018, 14:40:15 UTC | [TEST] Increased timeout for verifying ccr monitoring. | 09 November 2018, 14:44:26 UTC |
| 72b93ad | Christoph Büscher | 08 November 2018, 09:22:25 UTC | Preserve `date_histogram` format when aggregating on unmapped fields (#35254) Currently when aggregating on an unmapped date field (e.g. using a date_histogram) we don't preserve the aggregations `format` setting but instead use the default format. This can lead to loosing the aggregations `format` when aggregating over several indices where some of them contain unmapped date fields and are encountered first in the reduce phase. Related to #31760 | 09 November 2018, 14:36:55 UTC |
| 0bb2fa9 | Martijn van Groningen | 09 November 2018, 14:31:51 UTC | [TEST] increased the number of index and delete ops to make it less likely that all ops exist as soft delete docs. | 09 November 2018, 14:34:07 UTC |
| 59741ae | Jim Ferenczi | 09 November 2018, 12:15:22 UTC | [TEST] Fix LegacyHasParentQueryBuilderTests#testIllegalValues | 09 November 2018, 14:16:19 UTC |
| 9261894 | Martijn van Groningen | 09 November 2018, 13:24:27 UTC | [CCR] Get all auto follow patterns and no auto follow metadata (#35381) Return empty response when querying all auto follow patterns, but there is no auto follow metadata. | 09 November 2018, 13:25:28 UTC |
| bca9995 | Albert Zaharovits | 09 November 2018, 09:38:45 UTC | DOCS Auditing search queries (#35301) This documents how to include the search queries in the audit log. There is a catch, that even if enabling `emit_request_body`, which should output queries included in request bodies, search queries were not output because, implicitly, no REST layer audit event type was included. This folk knowledge is herein imprinted. | 09 November 2018, 11:32:10 UTC |
| 97adb4b | Marios Trivyzas | 09 November 2018, 10:32:38 UTC | SQL: Introduce IsNull node to simplify expressions (#35206) Add `IsNull` node in parser to simplify expressions so that `<value> IS NULL` is no longer translated internally to `NOT(<value> IS NOT NULL)` Replace `IsNotNullProcessor` with `CheckNullProcessor` to encapsulate both isNull and isNotNull functionality. Closes: #34876 Fixes: #35171 | 09 November 2018, 11:06:10 UTC |
| 58d3c70 | Nirmal Chidambaram | 30 June 2018, 18:17:37 UTC | has_parent builder: exception message/param fix (#31182) has_parent builder throws exception message that it expects a `type` while parser excepts `parent_type` | 09 November 2018, 10:12:45 UTC |
| 1e4440a | Colin Goodheart-Smithe | 09 November 2018, 08:21:08 UTC | Updates 6.5.0 release notes | 09 November 2018, 08:21:08 UTC |
| 4d0aba2 | Marios Trivyzas | 08 November 2018, 22:32:59 UTC | SQL: Handle null literal for AND and OR in `WHERE` (#35236) Change `nullable()` logic of AND and OR to false since in the Optimizer we cannot fold to null as we might be handling and expression in the SELECT clause. Introduce folding of null for AND and OR expressions in PruneFilter() since we now know that we are in HAVING or WHERE clause and we can fold `null` to `false` Fixes: #35088 Co-authored-by: Costin Leau <costin.leau@gmail.com> | 08 November 2018, 22:54:19 UTC |
| fe988a2 | Lisa Cawley | 08 November 2018, 21:53:09 UTC | [DOCS] Cleans up monitoring configuration steps (#35111) | 08 November 2018, 22:07:13 UTC |
| a3b2c72 | Jake Landis | 07 November 2018, 21:08:03 UTC | watcher: Fix integration tests to ensure correct start/stop of Watcher (#35271) Ensure that Watcher is correctly started and stopped between tests for SmokeTestWatcherWithSecurityIT, SmokeTestWatcherWithSecurityClientYamlTestSuiteIT, SmokeTestWatcherTestSuiteIT, WatcherRestIT, XDocsClientYamlTestSuiteIT, and XPackRestIT The change here is to throw an `AssertionError` instead of `break;` to allow the `assertBusy()` to continue to busy wait until the desired state is reached. closes #33291, closes #29877, closes #34462, closes #30705, closes #34448 | 08 November 2018, 20:41:42 UTC |
| c53b7d3 | Jack Conradson | 08 November 2018, 19:54:19 UTC | Scripting: Add back lookup vars in score script (#34833) (#35386) The lookup vars under params (namely _fields and _source) were inadvertently removed when scoring scripts were converted to using script contexts. This commit adds them back, along with deprecation warnings for those that should not be used. | 08 November 2018, 19:54:19 UTC |
| 5926a86 | Zachary Tong | 08 November 2018, 16:02:30 UTC | [Docs] Add painless context details for bucket_selector (#35162) Adds docs for the bucket_selector context, an example and corresponding doc test | 08 November 2018, 16:08:48 UTC |
| ef68276 | Martijn van Groningen | 08 November 2018, 15:26:14 UTC | [CCR] Rename leaderClient variables and parameters to remoteClient (#35368) | 08 November 2018, 15:27:11 UTC |
| 29bf3e6 | Russ Cam | 08 November 2018, 11:43:08 UTC | [Docs] Section header preceded by blank line (#34340) | 08 November 2018, 11:43:29 UTC |
| 1e1fd96 | Martijn van Groningen | 08 November 2018, 09:48:27 UTC | [CCR] Auto follow Coordinator fetch cluster state in system context (#35120) Auto follow Coordinator should fetch the leader cluster state using system context. | 08 November 2018, 10:15:36 UTC |
| c3478a5 | Jeff Hajewski | 08 November 2018, 10:09:03 UTC | Fixes fast vector highlighter docs per issue 24318. (#34190) The `fvh` highlighter does not support span queries. This fix updates the docs to add a warning stating the lack of span query support for `fvh`. | 08 November 2018, 10:10:02 UTC |
| 72e615a | Jason Tedor | 08 November 2018, 03:25:37 UTC | Add docs on JNA temp directory not being noexec (#35355) If the underlying mount point for the JNA temporary directory is mounted noexec on Linux, then the JVM will not be able to map the native code in as executable. This will prevent JNA from executing and will prevent Elasticsearch from being able to execute some functions that rely on native code (e.g., memory locking, and installing system call filters). We do not want to get into the business of catching exceptions and parsing messages towards this because these exception messages can change on us. We also do not want to jump through a lot of hoops to check the underlying mount point for noexec. Instead, we will rely on documentation to address this problem. This commit adds to the important system configuration section of the docs that the JNA temporary directory is not on a mount point with the noexec mount option. | 08 November 2018, 03:25:58 UTC |
| 6bd3f4c | Martijn van Groningen | 08 November 2018, 02:59:58 UTC | [CCR] Adjust list of dynamic index settings that should be replicated (#35195) Adjust list of dynamic index settings that should be replicated and added a test that verifies whether builtin dynamic index settings are classified as replicated or non replicated (whitelisted). | 08 November 2018, 03:14:05 UTC |
| e420b21 | Jason Tedor | 08 November 2018, 02:20:51 UTC | Replicate index settings to followers (#35089) This commit uses the index settings version so that a follower can replicate index settings changes as needed from the leader. Co-authored-by: Martijn van Groningen <martijn.v.groningen@gmail.com> | 08 November 2018, 02:47:13 UTC |
| 067e23c | Nhat Nguyen | 07 November 2018, 20:26:30 UTC | Use soft-deleted docs to resolve strategy for engine operation (#35230) A CCR test failure shows that the approach in #34474 is flawed. Restoring the LocalCheckpointTracker from an index commit can cause both FollowingEngine and InternalEngine to incorrectly ignore some deletes. Here is a small scenario illustrating the problem: 1. Delete doc with seq=1 => engine will add a delete tombstone to Lucene 2. Flush a commit consisting of only the delete tombstone 3. Index doc with seq=0 => engine will add that doc to Lucene but soft-deleted 4. Restart an engine with the commit (step 2); the engine will fill its LocalCheckpointTracker with the delete tombstone in the commit 5. Replay the local translog in reverse order: index#0 then delete#1 6. When process index#0, an engine will add it into Lucene as a live doc and advance the local checkpoint to 1 (seq#1 was restored from the commit - step 4). 7. When process delete#1, an engine will skip it because seq_no=1 is less than or equal to the local checkpoint. We should have zero document after recovering from translog, but here we have one. Since all operations after the local checkpoint of the safe commit are retained, we should find them if the look-up considers also soft-deleted documents. This PR fills the disparity between the version map and the local checkpoint tracker by taking soft-deleted documents into account while resolving strategy for engine operations. Relates #34474 Relates #33656 | 08 November 2018, 00:18:44 UTC |
| 900e711 | Martijn van Groningen | 07 November 2018, 19:41:27 UTC | Ignore date ranges containing 'now' when pre-processing a percolator query (#35160) Today when a percolator query contains a date range then the query analyzer extracts that range, so that at search time the `percolate` query can exclude percolator queries efficiently that are never going to match. The problem is that if 'now' is used it is evaluated at index time. So the idea is to rewrite date ranges with 'now' to a match all query, so that the query analyzer can't extract it and the `percolate` query is then able to evaluate 'now' at query time. | 07 November 2018, 19:51:25 UTC |
| e56aceb | Martijn van Groningen | 07 November 2018, 19:16:26 UTC | [CCR] Enforce auto follow pattern name restrictions (#35197) An auto follow pattern: * cannot start with `_` * cannot contain a `,` * can be encoded in UTF-8 * the length of UTF-8 encoded bytes is no longer than 255 bytes | 07 November 2018, 19:18:13 UTC |
| 0fdf5fc | Chris Cho | 07 November 2018, 16:01:35 UTC | [Docs] Improve Convert Processor description (#35280) Sometimes users are confused about whether they can use the Convert Processor for changing an existing fields type to other types even if the existing one is already ingested. This confusion is from the first line of description. Changing this and also adding a some detail to the code snippet. | 07 November 2018, 16:02:45 UTC |
| 3414a88 | Martijn van Groningen | 07 November 2018, 12:23:30 UTC | [CCR] Fail with a better error if leader index is red (#35298) as part of fetching history uuids from leader index. | 07 November 2018, 13:14:24 UTC |
| 4ecb79b | Vladimir Dolzhenko | 07 November 2018, 11:52:11 UTC | Fix DeleteRequest / GetRequest / UpdateRequest / ExplainRequest validation for null and/or empty id/type (#35314) Closes #35297 (cherry picked from commit a467a816bc1469837edbdb237e1bc99e4650ca2d) | 07 November 2018, 12:37:54 UTC |
| edd8277 | Marios Trivyzas | 07 November 2018, 11:08:32 UTC | SQL: Improve CircuitBreaker logic for SqlParser (#35300) Grammar's identifiers can be completely skipped from counting depths as they just add another level to the tree and they are always children of some other expression which gets counted. Increased maximum depth from 100 to 200. After testing on production configuration with -Xss1m, depths of at least 250 can be used, so being conservative we put the limit lower. Fixes: #35299 | 07 November 2018, 11:21:43 UTC |
| 1f83fe6 | Martijn van Groningen | 07 November 2018, 06:38:44 UTC | [CCR] Change resume follow api to be a master node action (#35249) In order to start shard follow tasks, the resume follow api already needs execute N requests to the elected master node. The pause follow API is also a master node action, which would make how both APIs execute more consistent. | 07 November 2018, 07:00:05 UTC |
| 98c8d12 | Lisa Cawley | 07 November 2018, 00:21:27 UTC | [DOCS] Adds CVE-2018-17244 to release notes (#35315) | 07 November 2018, 00:25:14 UTC |
| 870cc86 | Lisa Cawley | 06 November 2018, 20:18:55 UTC | [DOCS] Adds 6.5.0 release highlights page (#35312) | 06 November 2018, 20:18:55 UTC |
| 1e7d64e | debadair | 06 November 2018, 19:03:47 UTC | [DOCS] Added link to 6.4.3 RNs | 06 November 2018, 19:03:47 UTC |
| fe7e74b | Yannick Welsch | 06 November 2018, 18:33:48 UTC | Register Azure max_retries setting (#35286) This commit properly registers the Azure max_retries setting in the settings infrastructure, allowing this setting to be actually used. | 06 November 2018, 18:53:26 UTC |
| a2e8b85 | javanna | 06 November 2018, 16:47:33 UTC | [TEST] adjust skip for msearch yaml test This test had the parameters in the wrong place, so they ended up being ignored. After fixing the test (and making sure that the runner catches these errors), the parameters were read yet a skip is needed as max_concurrent_shard_requests is only supported from 6.5.0 on. Closes #34827 | 06 November 2018, 18:20:10 UTC |
| 9c2c341 | javanna | 06 November 2018, 16:03:26 UTC | add version 6.4.4 | 06 November 2018, 18:20:10 UTC |
| 3e8d12c | javanna | 06 November 2018, 16:02:36 UTC | add version 5.6.14 | 06 November 2018, 18:20:10 UTC |
| 372f5b7 | Zachary Tong | 06 November 2018, 17:18:29 UTC | [Docs] Add painless context details for bucket_script (#35142) Fleshes out the details of the bucket_script context, adds an example and corresponding doc test | 06 November 2018, 18:13:10 UTC |
| 8fa5939 | Jake Landis | 05 November 2018, 17:44:10 UTC | ingest: raise visibility of ingest plugin documentation (#35048) * move the set security user processor to the main documentation * link to plugin processors part of #33188 | 06 November 2018, 15:56:41 UTC |
| 3a59d5e | Jake Landis | 01 November 2018, 16:08:04 UTC | ingest: add common options to each processor's documentation (#35091) * adds `if`, `on_failure`, `tag`, and `ignore_failure` to table for each processor part of #33188 * added ingore_failure * fix whitespace noise | 06 November 2018, 15:56:35 UTC |
| 9dc2f1a | Gytis Šk | 06 November 2018, 15:45:10 UTC | Docs: Add section about range query for range type (#35222) This makes their interaction more discoverable. | 06 November 2018, 15:46:07 UTC |
| fa0f300 | Martijn van Groningen | 06 November 2018, 15:04:37 UTC | [CCR] Forgot missing return statement, Error was thrown if leader index had no soft deletes enabled, but it then continued creating the follower index. The test caught this bug, but very rarely due to timing issue. Build failure instance: ``` 1> [2018-11-05T20:29:38,597][INFO ][o.e.x.c.LocalIndexFollowingIT] [testDoNotCreateFollowerIfLeaderDoesNotHaveSoftDeletes] before test 1> [2018-11-05T20:29:38,599][INFO ][o.e.c.s.ClusterSettings ] [node_s_0] updating [cluster.remote.local.seeds] from [[]] to [["127.0.0.1:9300"]] 1> [2018-11-05T20:29:38,599][INFO ][o.e.c.s.ClusterSettings ] [node_s_0] updating [cluster.remote.local.seeds] from [[]] to [["127.0.0.1:9300"]] 1> [2018-11-05T20:29:38,609][INFO ][o.e.c.m.MetaDataCreateIndexService] [node_s_0] [leader-index] creating index, cause [api], templates [random-soft-deletes-templat e, one_shard_index_template], shards [2]/[0], mappings [] 1> [2018-11-05T20:29:38,628][INFO ][o.e.c.r.a.AllocationService] [node_s_0] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[leader- index][0]] ...]). 1> [2018-11-05T20:29:38,660][INFO ][o.e.x.c.a.TransportPutFollowAction] [node_s_0] [follower-index] creating index, cause [ccr_create_and_follow], shards [2]/[0] 1> [2018-11-05T20:29:38,675][INFO ][o.e.c.s.ClusterSettings ] [node_s_0] updating [cluster.remote.local.seeds] from [["127.0.0.1:9300"]] to [[]] 1> [2018-11-05T20:29:38,676][INFO ][o.e.c.s.ClusterSettings ] [node_s_0] updating [cluster.remote.local.seeds] from [["127.0.0.1:9300"]] to [[]] 1> [2018-11-05T20:29:38,678][INFO ][o.e.x.c.LocalIndexFollowingIT] [testDoNotCreateFollowerIfLeaderDoesNotHaveSoftDeletes] after test 1> [2018-11-05T20:29:38,678][INFO ][o.e.x.c.LocalIndexFollowingIT] [testDoNotCreateFollowerIfLeaderDoesNotHaveSoftDeletes] [LocalIndexFollowingIT#testDoNotCreateFoll owerIfLeaderDoesNotHaveSoftDeletes]: cleaning up after test 1> [2018-11-05T20:29:38,678][INFO ][o.e.c.m.MetaDataDeleteIndexService] [node_s_0] [follower-index/TlWlXp0JSVasju2Kr_hksQ] deleting index 1> [2018-11-05T20:29:38,678][INFO ][o.e.c.m.MetaDataDeleteIndexService] [node_s_0] [leader-index/FQ6EwIWcRAKD8qvOg2eS8g] deleting index FAILURE 0.23s J0 | LocalIndexFollowingIT.testDoNotCreateFollowerIfLeaderDoesNotHaveSoftDeletes <<< FAILURES! > Throwable #1: java.lang.AssertionError: > Expected: <false> > but: was <true> > at __randomizedtesting.SeedInfo.seed([7A3C89DA3BCA17DD:65C26CBF6FEF0B39]:0) > at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) > at org.elasticsearch.xpack.ccr.LocalIndexFollowingIT.testDoNotCreateFollowerIfLeaderDoesNotHaveSoftDeletes(LocalIndexFollowingIT.java:83) > at java.lang.Thread.run(Thread.java:748) ``` Build failure: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.5+intake/46/console | 06 November 2018, 15:06:12 UTC |
| b5ba739 | Marios Trivyzas | 06 November 2018, 14:40:16 UTC | SQL: Fix null handling for AND and OR in SELECT (#35277) Override `process()` in `BinaryLogicProcessor` which doesn't immediately return null if left or right argument is null, which is the behaviour of `process()` of the parent class `BinaryProcessor`. Also, add more tests for `AND` and `OR` in SELECT clause with literal. Fixes: #35240 | 06 November 2018, 14:41:59 UTC |
| 4788a10 | javanna | 06 November 2018, 12:36:22 UTC | [TEST] increase await timeout in RemoteClusterConnectionTests We have seen an improvement when we bumped the timeout from 1s to 5s, but there are still a few failures for this tests. With this commit we bump the timeout to 10 seconds hoping it will stop all the failures. | 06 November 2018, 12:37:08 UTC |
| 475927f | Igor Motov | 01 November 2018, 00:32:18 UTC | Fixes randomDateTimeZone method (#35145) The randomDateTimeZone method shouldn't return deprecated timezones this causes some tests to fail with deprecation warning. | 06 November 2018, 10:23:48 UTC |
| e01161c | Ryan Ernst | 30 October 2018, 18:15:34 UTC | Test: Filter out deprecated joda tzs in tests (#34868) This commit filters out usage of deprecated tzs by tests. These are tested separately and should not require checking for warnings on any test using random timezones. closes #34188 | 06 November 2018, 10:23:48 UTC |
| 8ad14b2 | Albert Zaharovits | 06 November 2018, 10:02:39 UTC | DOCS MINOR fix broken list format in migration.asciidoc (#35267) | 06 November 2018, 10:11:05 UTC |
| 52d204c | Martijn van Groningen | 06 November 2018, 07:42:47 UTC | [CCR] Improve error when operations are missing (#35179) Improve error when operations are missing | 06 November 2018, 07:43:49 UTC |
| 098fd78 | Martijn van Groningen | 06 November 2018, 07:00:34 UTC | [CCR] Add extra validation to unfollow api (#35245) Validate whether the follow index actually exists and whether the follow index actually has custom ccr metadata. | 06 November 2018, 07:05:13 UTC |
| f1289b9 | Jeff Soloshy | 06 November 2018, 06:49:18 UTC | [Docs] Minor formatting and wording fixes (#35278) | 06 November 2018, 06:50:44 UTC |
| 61287c8 | lcawl | 05 November 2018, 23:30:35 UTC | [DOCS] Fixes formatting error in auditing settings | 05 November 2018, 23:36:42 UTC |
| a21316b | Marios Trivyzas | 05 November 2018, 21:23:07 UTC | SQL: Introduce NotEquals node to simplify expressions (#35234) Add NotEquals node in parser to simplify expressions so that <value1> != <value2> is no longer translated internally to NOT(<value1> = <value2>) Closes: #35210 Fixes: #35233 | 05 November 2018, 21:34:37 UTC |
| 8bcc19d | Alexander Zhukov | 05 November 2018, 18:31:35 UTC | Doc: Drop an extra 'a' in snapshots.asciidoc (#35251) | 05 November 2018, 18:32:30 UTC |
| 04596fa | Nik Everett | 05 November 2018, 17:28:01 UTC | Reindex: Clean up docs around multi-index We have an example in `reindex`'s docs about copying from many indices at once. It doesn't work at the moment because we only allow a single type per index. We didn't notice it in the docs tests because those tests didn't copy any documents. This change: 1. Adds documents to the docs tests to fully exercise the snippet. 2. Fixes the example by moving all copied documents to the same type. 3. Moves the note about id collisions and expands on it because it is even more likely than before. Closes #35150 | 05 November 2018, 18:12:25 UTC |
| a7c1386 | Marios Trivyzas | 05 November 2018, 17:45:58 UTC | SQL: [tests] Fix select csv spec and enable it (#35239) Also, replace `||` and `&&` with `OR` and `AND` as the former are not SQL standard operators. | 05 November 2018, 17:49:41 UTC |
| 6311231 | Yannick Welsch | 05 November 2018, 15:15:19 UTC | [TEST] Fix testConcurrentTermIncreaseOnReplicaShard This test has a bug that got introduced during the refactoring of #32442. With 2 concurrent term increments, we can only assert under the operation permit that we are in the correct operation term, not that there is not already another term bump pending. Closes #34862 | 05 November 2018, 15:19:08 UTC |
| 6e8e326 | Martijn van Groningen | 05 November 2018, 11:51:42 UTC | [CCR] Change max_read_request_size default (#35247) This changes the max_read_request_size default from unlimited to 32MB. | 05 November 2018, 11:52:38 UTC |
| 58995b9 | Tim Vernum | 29 October 2018, 00:23:36 UTC | [TEST] Manually trigger resource watching (#34893) SSLTrustRestrictionsTests.testRestrictionsAreReloaded checks that the SSL trust configuration is automatically updated reapplied if the underlying "trust_restrictions.yml" file is modified. Since the default resource watcher frequency is 5seconds, it could take 10 second to run that test (as it waits for 2 reloaded). Previously this test set that frequency to a very low value (3ms) so that the elapsed time for the test would be reduced. However this caused other problems, including that the resource watcher would frequently run while the cluster was shutting down and files were being cleaned up. This change resets that watch frequency back to its default (5s) and then manually calls the "notifyNow" method on the resource watcher whenever the restrictions file is modified, so that the SSL trust configuration is reloaded at exactly the right time. Resolves: #34502 | 05 November 2018, 03:35:19 UTC |
| fc22662 | Boaz Leskes | 04 November 2018, 12:43:33 UTC | Engine.newChangesSnapshot may cause unneeded refreshes if called concurrently (#35169) When the engine is asked for historical operations, we check if some of the requested operations are not yet refreshed and if so we refresh before returning the operations. The refresh check is based on capturing the local checkpoint before each refresh and comparing that value to the one requested when `newChangesSnapshot` was called. If the requested range is above the captured local checkpoint we issue a refresh. This can currently cause unneeded extra refreshes if the method is called concurrently which may cause unwanted degradation in indexing performance. This is especially relevant for CCR where we always ask for a range below the global checkpoint. That range is guaranteed to be below the local checkpoint of the shard and one refresh is enough to serve multiple changes requests. This commit fixes this by introducing a dedicated mutex to make sure the test for whether a refresh is needed actually wait for concurrents for concurrent refreshes that were caused by another change refresh. Note that this is not a big change in semantics as refreshes are serialized by lucene anyway. I also opted not to keep the synchronization to the changes snapshot request only even if in theory we can apply it to all refreshes, not matter where they come from. | 04 November 2018, 12:56:33 UTC |
| 96af589 | Nhat Nguyen | 03 November 2018, 14:00:54 UTC | CCR/TEST: Limit indexing docs in FollowerFailOverIT (#35228) The suite FollowerFailOverIT is failing because some documents are not replicated to the follower. Maybe the FollowTask is not working as expected or the background indexers eat all resources while the follower cluster is trying to reform after a failover; then CI is not fast enough to replicate all the indexed docs within 60 seconds (sometimes I see 80k docs on the leader). This commit limits the number of documents to be indexed into the leader index by the background threads so that we can eliminate the latter case. This change also replaces a docCount assertion with a docIds assertion so we can have more information if these tests fail again. Relates #33337 | 03 November 2018, 14:19:45 UTC |
| 18bcf27 | Nhat Nguyen | 03 November 2018, 01:31:36 UTC | Add equals/hashCode to SeqNoStats (#35223) This commit adds equals/hashCode to SeqNoStats so we can verify it wholly in tests. | 03 November 2018, 02:43:36 UTC |
| 80c2ff6 | Nhat Nguyen | 02 November 2018, 12:49:55 UTC | Do not alloc full buffer for small change requests (#35158) Today we always allocate a full buffer (1024 elements) in a LuceneChangesSnapshot even though the requesting size is smaller. With this change, we will use the requesting size as the buffer size if it's smaller than the default batch size; otherwise uses the default batch size. | 02 November 2018, 22:46:23 UTC |
| 0edd3c5 | Nhat Nguyen | 02 November 2018, 16:27:48 UTC | TEST: Only check max_seq_no_of_updates when rollback (#35170) Currently, we assume that rollback always happens in the test testRestoreLocalHistoryFromTranslogOnPromotion. However, if the global checkpoint equals max_seq_no, we won't rollback. This causes the max_seq_no_of_updates assertion failed because max_seq_no_of_updates won't be advanced to the global checkpoint. With this commit, we assert max_seq_no_of_updates in two different paths. | 02 November 2018, 22:46:16 UTC |
| bbaf6ce | Lisa Cawley | 02 November 2018, 21:23:13 UTC | [DOCS] Move CCR overview pages (#34918) | 02 November 2018, 21:44:33 UTC |
| ff61ee1 | David Kyle | 02 November 2018, 15:12:47 UTC | Mute FollowerFailOverIT.testFollowIndexAndCloseNode Issue #33337 | 02 November 2018, 15:14:17 UTC |
| e11b2b7 | Nhat Nguyen | 02 November 2018, 11:01:46 UTC | CCR: Add NodeClosedException to retryable list (#35191) This change adds NodeClosedException to the retry-able exception list. | 02 November 2018, 11:10:57 UTC |
| 2fd0887 | Ryan Ernst | 14 October 2018, 22:54:49 UTC | Tests: Fix DateFormatter equals tests with locale (#34435) This commit removes randomization of locale for DateFormatter equals tests, instead using explicit locales. The test framework already randomizes locales, so the random choice of the second locale can sometimes be equal to the already chosen locale. Randomization also does not provide any extra protection, as the equality of DateFormatter does not implement equality of the locales itself. closes #34337 | 02 November 2018, 11:03:39 UTC |
| 7591555 | Marios Trivyzas | 02 November 2018, 09:37:54 UTC | SQL: Fix null handling for IN => painless script (#35124) Include `null` literals when generating the painless script for `IN` expressions. Previously, they were skipped, because of an issue that had been fixed with #35108. Fixes: #35122 | 02 November 2018, 10:14:46 UTC |
| 0051125 | Colin Goodheart-Smithe | 02 November 2018, 08:50:45 UTC | Updates 6.5.0 release notes | 02 November 2018, 08:50:45 UTC |
| d396ac5 | Nhat Nguyen | 02 November 2018, 01:58:03 UTC | CCR/TEST: Add debug log to testFailOverOnFollower | 02 November 2018, 02:31:31 UTC |
| dda218d | lcawl | 01 November 2018, 21:27:49 UTC | [DOCS] Fixes location of beta markup | 01 November 2018, 21:37:15 UTC |
| e2ebfb7 | Lee Hinman | 01 November 2018, 20:52:46 UTC | Enhance deprecation message when index name contains ':' (#34867) The message was a little unclear in that we will still support indices that have a ':' in the name in 7.0, we will only prevent index creation containing a ':' Relates to https://github.com/elastic/elasticsearch/issues/23892#issuecomment-432917004 | 01 November 2018, 20:53:29 UTC |
| b1112ff | Andy Bristol | 01 November 2018, 20:01:53 UTC | [test] quote base_path in repository tests | 01 November 2018, 20:11:21 UTC |
| 981738e | Julie Tibshirani | 01 November 2018, 19:41:07 UTC | Add a note around using separate indices for percolator queries and documents. (#35109) | 01 November 2018, 19:48:44 UTC |
| e7dcb15 | Julie Tibshirani | 01 November 2018, 19:02:55 UTC | Unmute AbstractQueryTestCase#testToQuery. The RangeQueryBuilderTests#testToQuery failures were fixed in #34868 and #35145. | 01 November 2018, 19:14:30 UTC |
| 8f589cc | lcawl | 01 November 2018, 18:50:30 UTC | [DOCS] Fixes formatting of dynamic settings links | 01 November 2018, 18:59:36 UTC |
| 2be338f | Julie Tibshirani | 30 October 2018, 17:19:12 UTC | Remove some documentation that only makes sense with multiple types. (#35066) * Remove a tip about ignore_above that only makes sense with multiple types. * Remove a line from the percolator documentation that refers to multiple types. | 01 November 2018, 18:43:31 UTC |
| 1f1930e | Andy Bristol | 01 November 2018, 18:05:59 UTC | mute JdbcCsvSpecIT #35176 | 01 November 2018, 18:05:59 UTC |
| 460e3eb | Itamar Syn-Hershko | 01 November 2018, 10:57:06 UTC | [Docs] Updating URL for Openstack Swift plugin (#34136) The repository plugin for Openstack Swift was developed originally by Wikimedia foundation but is now retired. This changes the link to the repo where the actively maintained fork lives now. | 01 November 2018, 10:58:29 UTC |
| 97c7f56 | Andrei Stefan | 01 November 2018, 09:30:05 UTC | SQL: handle wildcard expansion on incorrect fields (#35134) | 01 November 2018, 10:14:46 UTC |
| c94aeef | Marios Trivyzas | 01 November 2018, 09:23:49 UTC | SQL: Improve painless script generated from `IN` (#35055) Replace standard `||` and `==` painless operators with new `in` method introduced in `InternalSqlScriptUtils`. This allows the list of values to become a script variable which is replaced each time with the list of values provided by the user. Move In to the same package as InPipe & InProcessor Follow up to #34750 Co-authored-by: Costin Leau <costin.leau@gmail.com> | 01 November 2018, 09:36:20 UTC |
| e350f0a | Alexandru Rusanescu | 01 November 2018, 09:22:06 UTC | [Docs] Update query_cache.asciidoc (#33340) Add note about non-visibility of cache content. | 01 November 2018, 09:29:12 UTC |
| 3ff8895 | Seong-hyun, Oh | 31 October 2018, 21:15:46 UTC | Make XContentBuilder in AliasActions build `is_write_index` field (#35071) Make XContentBuilder in AliasesActions build `is_write_index` field | 31 October 2018, 22:01:19 UTC |
| 523cd64 | Costin Leau | 31 October 2018, 21:07:36 UTC | SQL: Register missing processors (#35121) Add registration (and tests) for missing processors in the serialization chain. Fix #35119 (cherry picked from commit f87a53451bae56c1a685c426373c6e9598bcb011) | 31 October 2018, 21:27:41 UTC |
| 90933d0 | David Turner | 31 October 2018, 19:21:24 UTC | Pre-populate unicast hosts files (#35136) Today when ESIntegTestCase starts some nodes it writes out the unicast hosts files each time a node starts its transport service. This does mean that a number of nodes can start and perform their first pinging round without any unicast hosts which, if the timing is unlucky and a lot of nodes are all started at the same time, can lead to a split brain as in #35052. Prior to #33554 this was unlikely to happen since the MockUncasedHostsProvider would always have yielded the existing hosts, so the timing would have to have been implausibly unlucky. Since #33554, however, it's more likely because the race occurs between the start of the first round of pinging and the writing of the unicast hosts file. It is realistic that new nodes will be configured with the existing nodes from startup, so this change reinstates that behaviour. Closes #35052. | 31 October 2018, 19:41:40 UTC |
| a1c80b8 | Qian Hong | 31 October 2018, 18:04:48 UTC | [Docs] Improve Redindex/Update/Delete By Query. (#35127) Fix a copy paste error and improve formatting in Redindex/Update/Delete By Query and fix formula in Update By Query. | 31 October 2018, 18:05:28 UTC |
| f62ba1d | Lisa Cawley | 31 October 2018, 16:18:14 UTC | [DOCS] Updates monitoring diagram (#35096) | 31 October 2018, 16:29:42 UTC |
| 5ec6dfd | Sue Gallagher | 31 October 2018, 14:16:36 UTC | [DOCS] Add info on calendar vs fixed interval. (#31638) Extensive edit to add additional information on the difference between calendar intervals and fixed-length intervals. | 31 October 2018, 14:27:53 UTC |
| de3d0e6 | Marios Trivyzas | 31 October 2018, 09:32:16 UTC | SQL: Fix NPE thrown if HAVING filter evals to null (#35108) Surround script with `nullSafeFilter` also for `AggFilter` translation. Fixed query translation tests to properly set `onAggs`. Fixes: #35107 | 31 October 2018, 09:43:49 UTC |
| 201bc02 | Colin Goodheart-Smithe | 31 October 2018, 09:14:21 UTC | Updates 6.4.3 release notes | 31 October 2018, 09:15:13 UTC |
| 506c511 | Marios Trivyzas | 30 October 2018, 21:31:29 UTC | SQL: [tests] Remove AbstractBuilderTestCase dep (#35099) Extend directly from `EsTestCase` to speed up execution. Fixes: #35098 | 30 October 2018, 21:40:00 UTC |
| cbb799e | Ryan Ernst | 30 October 2018, 20:24:18 UTC | Scripting: Add back params._source access in scripted metric aggs (#34777) (#34832) Access to special variables _source and _fields were accidentally removed in recent refactorings. This commit adds them back, along with a test. closes #33884 | 30 October 2018, 20:24:37 UTC |
| eb28e60 | Zachary Tong | 30 October 2018, 17:50:50 UTC | [Rollup] Proactively resolve index patterns in RollupSearch endoint (#34930) This changes the RollupSearch endpoint to proactively resolve index patterns. If the index pattern(s) match more than one rollup index, an exception is throw as before. But if the pattern only matches one rollup index, execution is allowed to continue (unlike before where it would assume all patterns were for raw data). This also allows the search endpoint to resolve aliases that point to a rollup index. Also tweaks the documentation to make this clear. Closes #34828 | 30 October 2018, 19:12:56 UTC |
| 0482e15 | Costin Leau | 30 October 2018, 18:17:20 UTC | SQL: Optimizer rule for folding nullable expressions (#35080) Add optimization for folding nullable expressions with a NULL argument. This is a variant of folding for the NULL case. Fix #34826 (cherry picked from commit 6abddd8ca614de9d47bd79c342113461b4b37526) | 30 October 2018, 18:47:36 UTC |
| 15d6d29 | Nik Everett | 30 October 2018, 18:12:59 UTC | Docs: Remove range notation from random score docs (#35093) The `random_score` function produces values between 0 (inclusive) and 1 (exclusive) and documented it with fancy methematical range notation. It is so fancy I thought it was a typo. This changes the documentation to use words. Relates to #35084 | 30 October 2018, 18:14:51 UTC |
| bcc8233 | Lisa Cawley | 30 October 2018, 15:38:22 UTC | [DOCS] Adds machine learning items to the 6.4.3 release notes (#35046) | 30 October 2018, 15:42:30 UTC |
| 3643f1f | Andrei Stefan | 30 October 2018, 14:18:52 UTC | Test for https://github.com/elastic/elasticsearch/issues/30054 bug (#35050) Added a test for a bug in Elasticsearch (https://github.com/elastic/elasticsearch/issues/32941) that had implications in SQL and activated another test that didn't work in the past | 30 October 2018, 14:29:03 UTC |
| 3f95d4c | Andrei Stefan | 30 October 2018, 13:52:05 UTC | SQL: Proper handling of nested fields at the beginning of the columns list (#35068) | 30 October 2018, 14:03:09 UTC |
| 9dd2cf3 | Colin Goodheart-Smithe | 30 October 2018, 12:46:39 UTC | Adds backport label to list to ignore (#35079) | 30 October 2018, 12:48:10 UTC |
