elastic/elasticsearch

ESQL should support a humanize option to quickly render values in human readable way.

Open

#136,533 创建于 2025年10月14日

在 GitHub 查看
 (17 评论) (0 反应) (0 负责人)Java (76,700 star) (25,882 fork)batch import
:Analytics/ES|QL>enhancementTeam:Analyticsgood first issue

描述

Description

When you deal with any sort of value that is in a unit that is not easy to comprehend as a human, like duration_in_nanos it is annoying to always have to manually perform some calculations like eval duration = duration_in_nanos / 1000 / 1000 to get to seconds resolution.

I would like to have a simple to_human(field, unit) and a to_human(field, unit, target_unit) conversion. It should support:

  • Duration
  • Bits (1000)
  • Bytes (1024)
  • Percent

We need two signatures for that function since sometimes I might not want to rely on the auto conversation and I want to fix everything to be displayed in GB. Otherwise I might end up with values of KB, MB, TB and so on in the same column.

贡献者指南

技术栈
java
领域
backenddatabase
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
JavaElasticsearch internalsESQL function implementation
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Look at existing ESQL functions like `date trunc` or `to string` in the Elasticsearch codebase, specifically in the `x pack/plugin/esql` module. Review the function registration and evaluation pattern. The issue defines two signatures. Consider the need for unit conversion and ensure the function handles different units (duration, bits, bytes, percent). Check any ongoing discussions in the comments for preferred implementation approach.