-
Notifications
You must be signed in to change notification settings - Fork 24.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOCS] Document range enrich policy #79607
Conversation
The yaml test snippets fail with an error and assertion error:
The assertion error can be fixed by moving I'm not sure why the actual error occurs. I will need to take a better look. |
Pinging @elastic/es-data-management (Team:Data Management) |
Pinging @elastic/es-docs (Team:Docs) |
I left the call in the spot where it originally was, interesting as it does look like te other paths could raise exceptions as well. Moving it makes sense, feels a little bit weird to do it as part of this PR? The remaining error is likely due to |
… to try catch. Fixes "java.lang.AssertionError: java.lang.AssertionError: callback must handle its own exceptions"
…, which breaks the test.
…y moving to try catch. Fixes "java.lang.AssertionError: java.lang.AssertionError: callback must handle its own exceptions"" -> moving to separate PR. This reverts commit 4d78c8e.
Yes, let's do this in a separate PR. |
Yes, it could be that actual error is caused by another test snippet. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mjmbischoff.
I pushed some commits to update the API docs, remove some unneeded snippet comments, publish your example, and clean up some of my own mistakes.
I left some suggestions and comments. My only major outstanding question is what happens if the processor's field
contains an array? The docs aren't clear right now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for clarifying @mjmbischoff. I pushed some additional commits to clean up some of my additions based on your comment and to move the include
statements to the right place.
If those changes look okay to you, this LGTM. Since I contributed, I'd like to get final approval from @martijnvg before merging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mjmbischoff and @jrodewig!
This LGTM
* upstream/master: (209 commits) Enforce license expiration (elastic#79671) TSDB: Automatically add timestamp mapper (elastic#79136) [DOCS] `_id` is required for bulk API's `update` action (elastic#79774) EQL: Add optional fields and limit joining keys on non-null values only (elastic#79677) [DOCS] Document range enrich policy (elastic#79607) [DOCS] Fix typos in 8.0 security migration (elastic#79802) Allow listing older repositories (elastic#78244) [ML] track inference model feature usage per node (elastic#79752) Remove IncrementalClusterStateWriter & related code (elastic#79738) Reuse previous indices lookup when possible (elastic#79004) Reduce merging in PersistedClusterStateService (elastic#79793) SQL: Adjust JDBC docs to use milliseconds for timeouts (elastic#79628) Remove endpoint for freezing indices (elastic#78918) [ML] add timeout parameter for DELETE trained_models API (elastic#79739) [ML] wait for .ml-state-write alias to be readable (elastic#79731) [Docs] Update edgengram-tokenizer.asciidoc (elastic#79577) [Test][Transform] fix UpdateTransformActionRequestTests failure (elastic#79787) Limit CS Update Task Description Size (elastic#79443) Apply the reader wrapper on can_match source (elastic#78988) [DOCS] Adds new transform limitation item and a note to the tutorial (elastic#79479) ... # Conflicts: # server/src/main/java/org/elasticsearch/index/IndexMode.java # server/src/test/java/org/elasticsearch/index/TimeSeriesModeTests.java
Adding docs for the range enrich policy Co-authored-by: James Rodewig <40268737+jrodewig@users.noreply.github.com>
Adding the docs similar to the match policy for the new range policy