From 0d34b4fea2293ef3cad7b34ff56f182b6b1f219e Mon Sep 17 00:00:00 2001 From: yangzhongjiao Date: Fri, 8 May 2026 08:56:23 +0000 Subject: [PATCH] feat(sql_lineage): add project_uid and db_service_uid to SQLLineageAnalyzeReqV1 Add ProjectUid and DBServiceUid fields to SQLLineageAnalyzeReqV1 so that downstream lineage analyzers can identify the project and DB service when expanding wildcard columns via metadata lookup. Refs: actiontech/dms-ee#736 --- sqle/api/controller/v1/sql_lineage.go | 2 ++ 1 file changed, 2 insertions(+) diff --git a/sqle/api/controller/v1/sql_lineage.go b/sqle/api/controller/v1/sql_lineage.go index e777561a55..0609b94118 100644 --- a/sqle/api/controller/v1/sql_lineage.go +++ b/sqle/api/controller/v1/sql_lineage.go @@ -10,6 +10,8 @@ type SQLLineageAnalyzeReqV1 struct { InstanceType string `json:"instance_type" form:"instance_type" valid:"omitempty,oneof=MySQL"` DefaultSchema string `json:"default_schema" form:"default_schema"` ResultColumnNames []string `json:"result_columns" form:"result_columns"` + ProjectUid string `json:"project_uid" form:"project_uid"` + DBServiceUid string `json:"db_service_uid" form:"db_service_uid"` } type SQLLineageAnalyzeResV1 struct {