Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Move `message` fields to `match_only_text`
See original GitHub issue7.14 is introducing a new field type called match_only_text which is meant as a more space-efficient variant of the text field type. Its only downsides are the following:
- no support for scoring: queries ignore index statistics and produce constant scores,
- span queries are unsupported,
- phrase and intervals queries run slower.
Other than that, this field supports the same feature set as text, and like text it doesn’t support aggregations. See https://www.elastic.co/guide/en/elasticsearch/reference/master/text.html#match-only-text-field-type if you would like to know more.
We are in the process of changing our built-in templates in Elasticsearch so that message fields get mapped as match_only_text rather than text. I think we should do the same in ECS as of Elasticsearch 7.14 (when this field gets released)?
Please let me know if there’s anything I can do to help.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
RFC 0023 is finished and the changes implemented in https://github.com/elastic/ecs/pull/1584
Thanks, @jpountz! We had been excitedly following the progress of
match_only_textto see where we could adopt it once it was ready. 😄I agree with looking to update
messagein ECS as well, and I think we may even consider additional fields within ECS where it makes sense.