jaegertracing/jaeger

query service "search" api 'limit', 'total' and 'offset' fields are not supplied on response

Open

#2,027 建立於 2020年1月17日

在 GitHub 查看
 (17 留言) (3 反應) (0 負責人)Go (18,974 star) (2,326 fork)batch import
area/storageenhancementhelp wanted

描述

Requirement - what kind of business use case are you trying to solve?

set of fields are not supplied on the query service search response

Service: jaeger query API: /apt/traces Current response:

{
  data: "...",
  total: 0,
  limit: 0,
  offset: 0
}

Response struct: https://github.com/jaegertracing/jaeger/blob/886b96574253a005ee7ebe74140098f3fe183606/cmd/query/app/http_handler.go#L56 Response part: https://github.com/jaegertracing/jaeger/blob/886b96574253a005ee7ebe74140098f3fe183606/cmd/query/app/http_handler.go#L238

Fields total, limit and offset are not supplied on the response part.

I am ready yo submit a PR if someone guide me to get these fields.

貢獻者指南

技術棧
go
領域
backendapi
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
needs maintainer response
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Go programming basicsFamiliarity with Jaeger query service
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
75
研究方向
The issue reports that the `/api/traces` response is missing `total`, `limit`, and `offset` fields. The response struct is defined in `cmd/query/app/http handler.go` at line 56, and the response is constructed at line 238. The developer should investigate how these fields are computed from the query result and ensure they are included in the response. The existing comments may contain hints, but maintainers should clarify the expected values. A good first step is to examine the data returned by the query service and confirm the source of these fields.