quickwit-oss / quickwit-oss/quickwit-datasource

Alias query missing

Open
#133 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
76
Forks
44
PR merge metrics
No merged PRs in 30d

Description

Hey, we are testing the QW instead of ES and what we find missing is the "Query aliasing". It seems that this is used by Grafana to build the legend. It seems that without aliasing the Grafana builds something up.

When selecting the ES data source we get Alias on The same row where we enter the Lucene query. I've googled around and it seems that the data source must support aliasing and is not something built in out of the box.

image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Grafana data-source query editor and trace how the Quickwit query is built compared with the Elasticsearch data source shown in the issue. Confirm where an alias would be entered and passed through, then verify that Grafana uses it to build the legend without affecting the query results.

Written by the indexing model from the issue text.

Assessment

Tech stack
grafana, typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.