Master #27
Merged
Master #27
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Add `parent` aggregation, a special single bucket aggregation that joins children documents to their parent.
With this commit we use the Gradle wrapper in documentation examples for the client benchmarks instead of Gradle itself. Relates elastic#35366
The class `MemoryCircuitBreaker` is unused so we remove all its traces from the code base. Relates elastic#35367
Also makes sure the awaitBusy for job stoppage is checked, so that we can fail if we timed out waiting for a job to stop. Closes elastic#35295
Improve error handling in the Indexer if an exception occurs during the very 1st retrieval (query execution)
Checkstyle
Adds docs for the bucket_selector context, an example and corresponding doc test
Currently we introduced a hard limit of 1024 to the number of fields a query can be expanded to in elastic#26541. Instead of using a hard limit, we should make this configurable. This change removes the hard limit check and uses the existing `max_clause_count` setting instead. Closes elastic#34778
This follows elastic#33552 , when the `_authenticate` API added a new `User` object for the API's response. This changes the `put_user` API to also employ a `User` object in the request. The User object changed slightly. A bug with put_user only putting/updating enabled (but not disabled) users has been fixed.
Today our OS information returned in node stats only returns a high-level name of the OS (e.g., "Linux"). Yet, for some uses this is too high-level and knowing at a finer level of granularity the underlying OS can be useful. This commit extracts the pretty name on Linux from /etc/os-release. This pretty name usually includes the Linux vendor and the Linux vendor version number (e.g., Fedora 28).
This commit adjusts the BWC version the OS pretty name field on OsInfo now that this field has been backported to the 6.x development branch.
This is related to elastic#34483. It introduces a namespaced setting for compression that allows users to configure compression on a per remote cluster basis. The transport.tcp.compress remains as a fallback setting. If transport.tcp.compress is set to true, then all requests and responses are compressed. If it is set to false, only requests to clusters based on the cluster.remote.cluster_name.transport.compress setting are compressed. However, after this change regardless of any local settings, responses will be compressed if the request that is received was compressed.
* Painless Context Doc: Add field context example relates to elastic#34829
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: elastic#35088 Co-authored-by: Costin Leau <costin.leau@gmail.com>
* [DOCS] ILM API Ref edits * [DOCS] Fixed endpoint for DELETE policy. * [DOCS] Removed comparison to setting index.lifecycle.name to null. * [DOCS] Fixed xrefs to explain API.
This commit fixes an assertion in the TcpTransportTests compresssion test.
* SNAPSHOTS: Use Path Style Access in S3 * Use path style access pattern to fix elastic#31608 * closes elastic#31608
We changed the way realm settings are defined, and this affects custom realms in SecurityExtensions. This change adds those details to the breaking changes docs. Relates: elastic#30241
This reverts commit f915475.
Many realm tests were written to use separate setting objects for "global settings" and "realm settings". Since elastic#30241 there is no distinction between these settings, so these tests can be cleaned up to use a single Settings object.
…34479) This change adds a logger for the query and fetch phases that prints all requests before their execution at the trace level. This will help debugging cases where an issue occurs during the execution since only completed queries are logged by the slow logs.
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.
* DISCOVERY: Fix RollingUpgradeTests * Don't manually manage min master nodes if not necessary * Remove some dead code * Allow for manually supplying list of seed nodes * Closes elastic#35178
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: elastic#34876 Fixes: elastic#35171
…ic#35381) Return empty response when querying all auto follow patterns, but there is no auto follow metadata.
…ikely that all ops exist as soft delete docs.
Move away from performing eager, fail-fast validation of mismatched mapping to a lazy evaluation based on the fields actually used in the query. This allows queries to run on the parts of the indices that "work" which is not just convenient but also a necessity for large mappings (like logging) where alignment is hard/impossible to achieve. Fix elastic#35659
IFNULL is a MySQL variant (also used in other DBs) which takes only 2 arguments and returns the first one that is not null. Closes: elastic#35749
Adds or corrects Javadoc on subclasses of Step.
…tic#35707) * [GEO] Add support to ShapeBuilders for building Lucene geometry This commit adds support for building lucene geometry from the ShapeBuilders. This is needed for integrating LatLonShape as the primary indexing approach for geo_shape field types. All unit and integration tests are updated to add randomization for testing both jts/s4j shapes and lucene shapes.
* Simplify complex `Runnable` by moving to `AbstractRunnable`
…astic#35603) Adds an XContent sub parser class that can to wrap another XContent parser at the beginning of an object and allow skiping all children in case of the parsing failure. It also uses this subparser to ignore the rest of the GeoJson shape if the parsing fails and we need to ignore the geoshape due to the ignore_malformed flag. Supersedes elastic#34498 Closes elastic#34047
…c#35721) This commit fixes an issue in the equals implementation for GlobalOperationPrivileges and adds few tests.
Add ISNULL as an alias of IFNULL as they have the same behaviour. Add basic test and docs. Closes: elastic#35781
* HLRC: Delete event from calendar * adjusting tests * adjusting code to make it more readable
By setting the cron to 2017, we ensure it won't trigger. This makes it easier to test because we know the job will _only_ be in STARTED, and we can ignore INDEXING states due to transient triggers. Closes elastic#35779
When there is no persistent tasks metadata we could hit a null pointer exception when executing a follower stats request. This is because we inspect the persistent tasks metadata. Yet, if no tasks have been registered, this is null (as opposed to empty). We need to avoid de-referencing the persistent tasks metadata in this case. That is what this commit does, and we add a test for this situation.
This commit moves the documentation and examples for the `index_prefixes` option on text fields to its own file, to bring it in line with other mapping parameters, and expands a bit on both.
) After elastic#35332 has been merged, we noticed some test failures like elastic#35597 in which one or more replica shards failed to be promoted as primaries because the primary replica re-synchronization never succeed. After some digging it appeared that the execution of the resync action was blocked because of the presence of a global cluster block in the cluster state (in this case, the "no master" block), making the resync action to fail when executed on the primary. Until elastic#35332 such failures never happened because the TransportResyncReplicationAction is skipping the reroute phase, the only place where blocks were checked. Now with elastic#35332 blocks are checked during reroute and also during the execution of the transport replication action on the primary. After some internal discussion, we decided that the TransportResyncReplicationAction should never be blocked. This action is part of the replica to primary promotion and makes sure that replicas are in sync and should not be blocked when the cluster state has no master or when the index is read only. This commit changes the TransportResyncReplicationAction to make obvious that it does not honor blocks. It also adds a simple test that fails if the resync action is blocked during the primary action execution. Closes elastic#35597
Add NVL as alias to IFNULL as they have the same behaviour. Add basic tests and docs. Closes: elastic#35782
* Forbid negative scores in functon_score query - Throw an exception when scores are negative in field_value_factor function - Throw an exception when scores are negative in script_score function Relates to elastic#33309
… TransportReplicationAction (elastic#35332)"" This reverts commit d3d7c01
Relates elastic#35822
Relates to elastic#35496
This endpoint was not previously documented as it was not particularly useful to end users. However, since the HLRC will support the endpoint we need some documentation to link to. The purpose of the endpoint is to provide defaults and limits used by ML. These are needed to fully understand configurations that have missing values because the missing value means the default should be used. Relates elastic#35777
…#35828) We didn't check that the ExplainLifecycleRequest was constructed with at least one index before, now that we do we must also make sure the tests mutateInstance() method used in equals/hashCode checks doesn't accidentally create an empty index array. Closes elastic#35822
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
56 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
gradle check?