entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://www.elastic.co/guide/en/kibana/current/index-patterns.html|1|https://www.elastic.co/guide/en/kibana/current/supported-aggregations.html|2|https://www.elastic.co/guide/en/elasticsearch/reference/7.9/search-aggregations-bucket-terms-aggregation.html|3|https://www.elastic.co/guide/en/elasticsearch/reference/current/keyword.html|4|https://www.elastic.co/guide/en/kibana/current/supported-aggregations.html#visualize-bucket-aggregations|5|https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html|6|https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html#_multi_fields|7|https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-fields.html|blocks|key|14kbt|text|Kibana使用index+patterns作为一个关键概念。它知道链接的索引和这些索引的底层字段结构(索引映射)。根据这些索引模式，Kibana可以确定哪些aggregations与特定字段兼容。|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|dbism|例如，terms+aggregation处理keyword类型的字段或其他适用于bucket+aggregations的data+types。对于文本字段，您需要启用fielddata才能使用术语聚合。|4qf6f|如果缺少特定字段的聚合，请检查使用具有不同数据类型的multi-field是否可以解决此问题。然后，在kibana中更新索引模式，您将能够在新的multi-field上进行聚合。|lhqf^0|8|E|0|27|C|1|0|3|H|2|M|7|3|14|J|4|1O|A|5|0|Q|B|6|20|B|7|0^^$0|$1|$2|3|4|5|6|$7|8]]|9|$2|3|4|5|6|$7|A]]|B|$2|3|4|5|6|$7|C]]|D|$2|3|4|5|6|$7|E]]|F|$2|3|4|5|6|$7|G]]|H|$2|3|4|5|6|$7|I]]|J|$2|3|4|5|6|$7|K]]|L|$2|3|4|5|6|$7|M]]]|N|@$O|P|Q|R|2|S|T|13|U|@]|V|@$W|14|X|15|O|16]|$W|17|X|18|O|19]]|6|$]]|$O|Y|Q|Z|2|S|T|1A|U|@]|V|@$W|1B|X|1C|O|1D]|$W|1E|X|1F|O|1G]|$W|1H|X|1I|O|1J]|$W|1K|X|1L|O|1M]]|6|$]]|$O|10|Q|11|2|S|T|1N|U|@]|V|@$W|1O|X|1P|O|1Q]|$W|1R|X|1S|O|1T]]|6|$]]|$O|12|Q|-4|2|S|T|1U|U|@]|V|@]|6|$]]]]

Kibana uses <a href="https://www.elastic.co/guide/en/kibana/current/index-patterns.html" rel="nofollow noreferrer">index patterns</a> as a key concept. It knows the linked indices and the underlying field structure (index mapping) of those indices. Based on these index patterns Kibana can determine which <a href="https://www.elastic.co/guide/en/kibana/current/supported-aggregations.html" rel="nofollow noreferrer">aggregations</a> are compatible with a specific field.
For example, the <a href="https://www.elastic.co/guide/en/elasticsearch/reference/7.9/search-aggregations-bucket-terms-aggregation.html" rel="nofollow noreferrer">terms aggregation</a> works on fields of type <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/keyword.html" rel="nofollow noreferrer">keyword</a> or other <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html" rel="nofollow noreferrer">data types</a> suitable for <a href="https://www.elastic.co/guide/en/kibana/current/supported-aggregations.html#visualize-bucket-aggregations" rel="nofollow noreferrer">bucket aggregations</a>. For text fields, you´ll need to enable fielddata to use the terms aggregation.
If you are missing an aggregation for a specific field, check if using a <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-types.html#_multi_fields" rel="nofollow noreferrer">multi-field</a> with a different data type will solve it. Afterward, update the index pattern in kibana and you´ll be able to aggregate on the new <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-fields.html" rel="nofollow noreferrer">multi-field</a>.

I am working on a platform that integrates Elasticsearch into itself.
Some part of this software is basically a kind of front-end for Elasticsearch.
Kibana somehow knows which aggregations a specific Elasticsearch data type supports.
I have examined the HTTP requests sent by Kibana, but I could not find where that information originates. (Maybe, I was not thorough.)
So, my question is:
How does Kibana determine which aggregations an Elasticsearch data type supports?
Is it possible to get that via the Elasticsearch API, or was it hard-coded on the client-side (in Kibana)?
Example:
<a href="https://i.stack.imgur.com/1CZom.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/1CZom.png" alt="Kibana" /></a>

How does Kibana know the supported aggregations of an (Elasticsearch) data type?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

 我正在开发一个将Elasticsearch集成到自身的平台。这个软件的某些部分基本上是Elasticsearch的一种前端。 Kibana以某种方式知道特定Elasticsearch数据类型支持哪些聚合。我检查了Kibana发送的HTTP请求，但我找不到该信息的来源。(也许，我还不够彻底。) 所以，我的问题是: Kibana如何确定Elasticsearch数据类型支持哪些聚合？有没有可能通过E

问Kibana如何知道(Elasticsearch)数据类型的支持聚合？
EN

回答 1

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Kibana如何知道(Elasticsearch)数据类型的支持聚合？EN