Test/kibana manticore handling#3104
Merged
Merged
Conversation
5 tasks
KlimTodrik
approved these changes
Feb 19, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Type of Change (select one):
Description of the Change:
Added a CLT test that verifies that an issue where the
_id fieldin the response to a_searchendpoint query was returned as a number(1)instead of a string(“1”)has been fixed. This was causing problems when integrating with Kibana, as Kibana expects_idto be a string. Now the_idfield is always returned as astring, which ensures correct operation with Kibana and other tools that expect string identifiers.Related Issue (provide the link):