KusionStack / KusionStack/karpor

Design: Search DSL

Open
#206 0 comments 0 reactions 0 assignees View on GitHub
area/search priority/important-longterm
Dominant language
Go
Stars
1.7k
Forks
113
PR merge metrics
No merged PRs in 30d

Description

### What would you like to be added?

Design the Search DSL.

### Why is this needed?

Considering the low learning cost of SQL for developers, only the SQL search method is supported in Karpor v0.4.0. However, in some search scenarios, providing specialized DSLs will simplify the search and improve the experience.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing SQL search method referenced in the issue and how search scenarios are currently represented. The issue names no files or tests, so the first step is to identify the relevant search entry points and establish the Search DSL's scope and requirements. Done means an agreed design that improves search usability without relying only on SQL.

Written by the indexing model from the issue text.

Assessment

Domain
search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.