Fix api query context

[shivanshuraj1333]

Important

Update query context handling in http_handler.go and translator.go for producer-topic-throughput.

• Behavior:
  • Change query context in getPartitionOverviewLatencyData() in http_handler.go from partition_latency to producer-topic-throughput.
• Query Handling:
  • Remove producer-topic-throughput from conditional check in BuildClickHouseQuery() in translator.go.

^{This description was created by for 728ec96. It will automatically update as commits are pushed.}

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 728ec96 in 42 seconds

More details

• Looked at 26 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. pkg/query-service/app/integrations/messagingQueues/kafka/translator.go:256

• Draft comment:
  The 'producer-topic-throughput' context was removed from the conditional check, but it is still used in the code. Ensure that this context is handled correctly elsewhere in the codebase.
• Reason this comment was not posted:
  Comment did not seem useful.

2. pkg/query-service/app/integrations/messagingQueues/kafka/translator.go:254

• Draft comment:
  Do not add non-ClickHouse related functions like producer-topic-throughput to BuildClickHouseQuery. Use the DAO in the telemetry instance instead.
• Reason this comment was not posted:
  Marked as duplicate.

Workflow ID: wflow_TM7Cc1hkFj3cJB21

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[request-info]

We would appreciate it if you could provide us with more info about this issue/pr!

[prashant-shahi]

@shivanshuraj1333 I believe you need to move the environment to the actual command that is executed instead of the CI environment.

export KAFKA_SPAN_EVAL="true"